1st) sorry about messing up the thread, it was accidental. 2nd) so, I can recover portage like you suggested, but then the instructions want me to upgrade portage again, and that brings the same problem back. There was, however, a message that I saw this time in the emerging of portage that mentioned that some python modules were put in '/var/tmp/portage/portage-2.0.49-r13/ image/usr/lib/python2.2/site-packages/' However that directory does not exist, and emerge still complains of missing modules.
Lewis On Tue, 2003-10-14 at 07:27, Mike Williams wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Tuesday 14 October 2003 06:27, Nick Rout wrote: > > > I just installed the new portage update, and the result is this output > > > from any portage command: > > > > > > [EMAIL PROTECTED] ultraman $ emerge -p world > > > Traceback (most recent call last): > > > File "/usr/bin/emerge", line 10, in ? > > > import > > > emergehelp,xpak,string,re,commands,time,shutil,traceback,atexit,signal > > > File "/usr/lib/portage/bin/emergehelp.py", line 7, in ? > > > from output import * > > > ImportError: No module named output > > > > > > > > > The only thing I can think of that might be a problem is that I upgraded > > > to python 2.3, and then I remember running some program that updated > > > portage to use python 2.3. Is is possible that I need to rerun that > > > program, and if so, what is it? > > > > don't start a new thread by replying to an existing message. it only > > creates threading problems. > > Well spoken that man! > > But to help Lewis, try looking at > /usr/portage/sys-apps/portage/files/README.RESCUE > > - -- > Mike Williams > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.2.3 (GNU/Linux) > > iD8DBQE/i92xInuLMrk7bIwRAnUiAJ48GVg3HioMi/ZbdoYrr+T9NCTl8ACcD3pR > kPo/u4yfU1fT6JbEXl3PLBk= > =ijNJ > -----END PGP SIGNATURE----- > > -- > [EMAIL PROTECTED] mailing list > -- [EMAIL PROTECTED] mailing list
