emerge =sys-apps/dbus-0.60-r4 on amd64 (but I think it's platform independ bug :-)) * Applying dbus-0.60-qdbusmarshall.patch ... [ ok ] * Cannot find $EPATCH_SOURCE! Value for $EPATCH_SOURCE is: * * /portage/sys-apps/dbus/files/dbus-0.60--mono-arguments.patch * ( dbus-0.60--mono-arguments.patch ) !!! ERROR: sys-apps/dbus-0.60-r4 failed. Call stack: ebuild.sh, line 1894: Called dyn_unpack ebuild.sh, line 694: Called src_unpack dbus-0.60-r4.ebuild, line 58: Called epatch 'unpack' !!! Cannot find $EPATCH_SOURCE! !!! If you need support, post the topmost build error, and the call stack if relevant.
There is an extra "-" in this line from the ebuild epatch "${FILESDIR}"/${PN}-0.60--mono-arguments.patch change it to: epatch "${FILESDIR}"/${PN}-0.60-mono-arguments.patch run a new digest and then it will compile okay.
After that: >>> Unpacking dbus-0.60.tar.gz to /var/tmp/portage/dbus-0.60-r4/work * Cannot find $EPATCH_SOURCE! Value for $EPATCH_SOURCE is: * * /overlay/sys-apps/dbus/files/dbus-0.60-gcj-2.patch * ( dbus-0.60-gcj-2.patch ) !!! ERROR: sys-apps/dbus-0.60-r4 failed. Call stack: ebuild.sh, line 1894: Called dyn_unpack ebuild.sh, line 694: Called src_unpack dbus-0.60-r4.ebuild, line 48: Called epatch 'unpack' !!! Cannot find $EPATCH_SOURCE! !!! If you need support, post the topmost build error, and the call stack if relevant.
Try another `emerge sync`. I only had the problem with dbus-0.60--mono-arguments.patch. After that it compiled.
No, still same. Huh, it looks for it in overlay even if i repair it in portage. In make.conf is set PORTDIR=/portage and PORTDIR_OVERLAY=/overlay and if i digesting it says: Appending /portage to PORTDIR_OVERLAY... >>> Generating digest file... ... Maybe is problem here, but very weird...
Oh gotcha, overlay have priority ... only deleting that in overlay works :)
Confirmed on my system, amd64 W
*** Bug 121224 has been marked as a duplicate of this bug. ***
*** Bug 121454 has been marked as a duplicate of this bug. ***
Right.. So this is fixed.
