I think the output of emerge says it best: >>> Emerging (10 of 41) sys-apps/openrc-0.4.3 * openrc-0.4.3.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] >>> Unpacking source... >>> Unpacking openrc-0.4.3.tar.bz2 to /var/tmp/portage/sys-apps/openrc-0.4.3/work * Applying 0001-msg-style.patch ... [ ok ] * Applying 0002-useful-functions.patch ... [ ok ] * Applying 0003-KV.patch ... [ ok ] * Applying 0004-svn-version.patch ... * Failed Patch: 0004-svn-version.patch ! * ( /usr/portage/sys-apps/openrc/files/0.4.2/0004-svn-version.patch ) * * Include in your bugreport the contents of: * * /var/tmp/portage/sys-apps/openrc-0.4.3/temp/0004-svn-version.patch-28705.out * * ERROR: sys-apps/openrc-0.4.3 failed. * Call stack: * ebuild.sh, line 49: Called src_unpack * environment, line 2616: Called epatch '/usr/portage/sys-apps/openrc/files/0.4.2/0001-msg-style.patch' '/usr/portage/sys-apps/openrc/files/0.4.2/0002-useful-functions.patch' '/usr/portage/sys-apps/openrc/files/0.4.2/0003-KV.patch' '/usr/portage/sys-apps/openrc/files/0.4.2/0004-svn-version.patch' * environment, line 1124: Called epatch '/usr/portage/sys-apps/openrc/files/0.4.2/0004-svn-version.patch' * environment, line 1260: Called die * The specific snippet of code: * die "Failed Patch: ${patchname}!"; * The die message: * Failed Patch: 0004-svn-version.patch! * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/sys-apps/openrc-0.4.3/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/sys-apps/openrc-0.4.3/temp/environment'. * Reproducible: Always Steps to Reproduce: 1. ACCEPT_KEYWORDS="~x86" 2. emerge --sync 3. emerge openrc or emerge world (or variants thereof that pull in openrc-0.4.3) Actual Results: Emerge fails. Something related to svn. Expected Results: Updated openrc.
Created attachment 181684 [details] Output for failed 0004-svn-version.patch The original reporter didn't attach the output from the failed patch, so here's mine!
Looks like it's fixed in CVS now....
It seems to have been fixed. I synced again and ran a world update. Emerge updated java ahead of openrc - I don't know if that had any influence on it, but openrc emerged fine now.
Yep, I was just about to mark it fixed when you beat me to it... http://sources.gentoo.org/viewcvs.py/gentoo-x86/sys-apps/openrc/openrc-0.4.3.ebuild?rev=1.3&view=markup
