Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 462701 - www-client/chromium-9999-r1 27.0.1450.0 Build 189789 Failed Patch chromium-ppapi-r0.patch
Summary: www-client/chromium-9999-r1 27.0.1450.0 Build 189789 Failed Patch chromium-pp...
Status: RESOLVED WORKSFORME
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Chromium Project
URL:
Whiteboard:
Keywords:
: 462896 (view as bug list)
Depends on:
Blocks:
 
Reported: 2013-03-22 16:05 UTC by Jeff Kowalczyk
Modified: 2013-03-24 19:33 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
emerge --info (emerge-info.txt,5.83 KB, text/plain)
2013-03-22 16:33 UTC, Jeff Kowalczyk
Details
chromium-ppapi-r0.patch.out (chromium-ppapi-r0.patch.out,2.89 KB, text/plain)
2013-03-22 16:34 UTC, Jeff Kowalczyk
Details
build.log (build.log,297.19 KB, text/plain)
2013-03-22 16:35 UTC, Jeff Kowalczyk
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jeff Kowalczyk 2013-03-22 16:05:01 UTC
Building www-client/chromium-9999-r1 as of 27.0.1450.0 Build 189789 results in failed patch chromium-ppapi-r0.patch. Info attached.

Reproducible: Always
Comment 1 Jeff Kowalczyk 2013-03-22 16:33:41 UTC
Created attachment 342921 [details]
emerge --info
Comment 2 Jeff Kowalczyk 2013-03-22 16:34:31 UTC
Created attachment 342923 [details]
chromium-ppapi-r0.patch.out
Comment 3 Jeff Kowalczyk 2013-03-22 16:35:26 UTC
Created attachment 342925 [details]
build.log
Comment 4 Paweł Hajdan, Jr. (RETIRED) gentoo-dev 2013-03-22 17:44:12 UTC
Please sync your tree (for some reason you have a recent timestamp, but maybe you're using an overlay).

This has been fixed a week ago: <http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/www-client/chromium/chromium-9999-r1.ebuild?r1=1.180&r2=1.181>
Comment 5 Mike Gilbert gentoo-dev 2013-03-24 19:33:44 UTC
*** Bug 462896 has been marked as a duplicate of this bug. ***