Platform is SUSE 10 Enterprise SP 1. Emerging virtual/editor-0 fails (during the `emerge -u system step'). This is seen in the console log (the path /local/scratch/portage/virtual/editor-0/image directory exists and is a directory but the path /local/scratch/portage/virtual/editor-0/image/local/tmp/j/ does not): >>> Emerging (10 of 20) virtual/editor-0 * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] >>> Unpacking source... >>> Source unpacked in /local/scratch/portage/virtual/editor-0/work >>> Compiling source in /local/scratch/portage/virtual/editor-0/work ... >>> Source compiled. >>> Test phase [not enabled]: virtual/editor-0 >>> Install editor-0 into /local/scratch/portage/virtual/editor-0/image/local/tmp/j/ category virtual >>> Completed installing editor-0 into /local/scratch/portage/virtual/editor-0/image/local/tmp/j/ /local/tmp/j/usr/lib/portage/bin/misc-functions.sh: line 45: cd: /local/scratch/portage/virtual/editor-0/image/local/tmp/j/: No such file or directory * ERROR: virtual/editor-0 failed: * cd failed * * Call stack: * misc-functions.sh:851: <call install_qa_check> * misc-functions.sh: 45: cd "${ED}" || die "cd failed"
This is a portage regression present in 2.2.00.13825 but not 2.2.00.13683. I have masked the bad portage for now because I do not know what the problem is.
ah, this has nothing to do with virtuals. It has to do with portage not creating ${ED} anymore for some reason.
Index: bin/ebuild.sh =================================================================== --- bin/ebuild.sh (revision 13804) +++ bin/ebuild.sh (working copy) @@ -1433,7 +1433,7 @@ src_compile src_install src_test" local x y default_func="" - for x in pkg_nofetch src_unpack src_test ; do + for x in pkg_nofetch src_unpack src_install src_test ; do declare -F $x >/dev/null || \ eval "$x() { _eapi0_$x \"\$@\" ; }" done revision 13826
fixed in portage-2.2.00.13827
Confirming: Successful bootstrapping on SUSE 10 this morning.
