Bug 17010 – After emerge -u world the emerge command is gone: Command can not be found

• Product: Portage Development
• Status: RESOLVED FIXED

[Description Maurits Lamers 2003-03-07 02:59:47 UTC]

After emerge -u world the process deletes the emerge binary and all other 
binaries it uses. I guess it was emerging portage and deleted the binaries it 
just created.

Reproducible: Always
Steps to Reproduce:
1.emerge -u world
2.emerge rsync
3.

Actual Results:  
- bash: no such command

Expected Results:  
rsync the portage tree

After copying a few of the lost binaries from an extracted stage file it only 
can show what packages still have to be updated and the only package it shows 
is the portage package. Emerge sync possible, Emerge -p possible, emerge -u 
portage doesn't work

[Comment 1 Maurits Lamers 2003-03-07 03:18:11 UTC]

Explanation of Emerge -u portage doesn't work:

Traceback (most recent call last):
  File "/usr/bin/emerge", line 1641, in ?
    mydepgraph.merge(mydepgraph.altlist())
  File "/usr/bin/emerge", line 1037, in merge
    retval=portage.doebuild(y,"merge",myroot,edebug)
  File "/usr/lib/python2.2/site-packages/portage.py", line 1242, in doebuild
    retval=spawn("/usr/sbin/ebuild.sh setup unpack compile install")
  File "/usr/lib/python2.2/site-packages/portage.py", line 857, in spawn
    os.execve(mycommand,myargs,settings.environ())
OSError: [Errno 2] No such file or directory

[Comment 2 Martin Holzer (RETIRED) 2003-03-07 03:24:23 UTC]

If your version of Portage dies for some reason, try using the
portage-rescue package as follows for Gentoo Linux 1.0+ systems:

SUBSTITUTE A FILE THAT EXISTS FOR THE EXAMPLE VERSION BELOW.
IF AN ARCHITECTURE IS SPECIFIED IN THE FILENAME BE SURE IT IS
THE CORRECT ONE FOR YOUR ARCH.

If you are not in this directory, you need to change to:
# cd /usr/portage/sys-apps/portage/files/

Run the following to extract the tarball (substitute your arch for 'x86')
# tar xjpUvf portage-rescue-2.0.44-x86.tbz2 -C /

You'll see a warning about garbage at the end of the tarball/bzip2.  That's
normal and not a problem.  That should get Portage up and running again.

Immediately after that finishes do the following:
# emerge rsync
# emerge portage

Everything should be fine from then on.

Best Regards,

Gentoo Linux

[Comment 3 Martin Holzer (RETIRED) 2003-05-22 14:12:03 UTC]

is this still a issue ?

[Comment 4 Maurits Lamers 2003-05-23 07:41:33 UTC]

Well, I don't know if it is still possible to lose the emerge command during emerge -u world, but the solution given (comment #2) worked fine. 

[Comment 5 Martin Holzer (RETIRED) 2003-10-15 09:49:44 UTC]

closing as fixed with latest portage