FEATURES=buildpkg emerge bc emerge -C bc ... uCpie portage-pkg # emerge -K bc Calculating dependencies ...done! >>> emerge (1 of 1) sys-devel/bc-1.06-r6 to / >>> extracting info /usr/lib/portage/bin/ebuild.sh: line 1704: /var/db/pkg/sys-devel/bc-1.06-r6/bc-1.06-r6.ebuild: No such file or directory !!! ERROR: sys-devel/bc-1.06-r6 failed. !!! Function , Line 1704, Exitcode 1 !!! error sourcing ebuild !!! If you need support, post the topmost build error, NOT this status message. >>> extracting bc-1.06-r6 >>> Merging sys-devel/bc-1.06-r6 to / --- /usr/ --- /usr/bin/ >>> Regenerating /etc/ld.so.cache... * Caching service dependencies... >>> sys-devel/bc-1.06-r6 merged. >>> clean: No packages selected for removal. >>> Auto-cleaning packages ... >>> No outdated packages were found on your system. uCpie portage-pkg # emerge -K bc Calculating dependencies ...done! >>> emerge (1 of 1) sys-devel/bc-1.06-r6 to / >>> extracting info >>> extracting bc-1.06-r6 >>> Merging sys-devel/bc-1.06-r6 to / --- /usr/ --- /usr/bin/ >>> Safely unmerging already-installed instance... Notice the first merge of the binary package produces an error. I'm not sure how to report this or whats up with the root reason but I'd figure I'd leave it here as a mental note. But to me it seems that when merging a binary package we should not assume that /var/db/pkg/$CATEGORY/$P-$PR/$P-$PR.ebuild would automaticly exist. line 1704 btw is the. source ${EBUILD} || die "error sourcing ebuild" uCpie portage-pkg # emerge -V info Portage 2.0.51.19 (uclibc/x86/2.4, gcc-3.3.5-20050130, uclibc-0.9.27-r0, 2.4.30-hardened-r0 i686)
Created attachment 56667 [details, diff] portage-2.0.51.19-ebuild-phase-setup-binarypkg-fix.patch Corrects the errror handling in ebuild.sh
Created attachment 65077 [details, diff] portage-2.0.51.22-ebuild-phase-setup-binarypkg-fix.patch The Problem still exists in portage-2.0.51.22-r2. I rewrite the patch, that is can be applied cleanly to 2.0.51.22-r2. Cheers Nicolas
*** This bug has been marked as a duplicate of 85083 ***
