This is a vicious circle. I unmerged 'supersed', which removed /usr/bin/sed binary. Now "emerge sed" fails because portage cannot find "sed" utility. Doh! Not sure whether this can be helped, though, but I thought I'd file a bug anyway. ;^) bashful root # emerge sed Calculating dependencies ...done! >>> emerge sys-apps/sed-3.02.80-r4 to / >>> md5 ;-) sed-3.02.80.tar.gz >>> Unpacking source... >>> Unpacking sed-3.02.80.tar.gz /usr/sbin/ebuild.sh: sed: command not found >>> Source unpacked. /usr/sbin/ebuild.sh: ./configure: No such file or directory !!! ERROR: The ebuild did not complete successfully. !!! Function src_compile, Line 3, Exitcode 127 !!! (no error message) !!! emerge aborting on /usr/portage/sys-apps/sed/sed-3.02.80-r4.ebuild .
yes yes, I know. supersed is now installed as ssed
well, it's not fixed but there's nothing much I can do about this one, since supersed already installs itself as ssed and the system sed won't be touched anymore...