Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 42869 - emerge fails completely after upgrade to python 2.3.3
Summary: emerge fails completely after upgrade to python 2.3.3
Status: RESOLVED FIXED
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Core - Interface (emerge) (show other bugs)
Hardware: All Linux
: High blocker (vote)
Assignee: Portage team
URL:
Whiteboard:
Keywords:
: 42868 (view as bug list)
Depends on:
Blocks:
 
Reported: 2004-02-25 04:25 UTC by Michael Knappe
Modified: 2004-04-09 00:55 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Knappe 2004-02-25 04:25:16 UTC
I am going to give you the whole story:

I started an "emerge -u world". It did install/update the following:

1077675551:  >>> AUTOCLEAN: sys-apps/man-pages
1077675556: === Unmerging... (sys-apps/man-pages-1.64)
1077675568:  >>> unmerge success: sys-apps/man-pages-1.64
1077675572:  ::: completed emerge (1 of 95) sys-apps/man-pages-1.65 to /
1077675572:  >>> emerge (2 of 95) sys-devel/libtool-1.4.3-r3 to /
1077675572:  === (2 of 95) Cleaning (sys-devel/libtool-1.4.3-r3::/usr/portage/sys-devel/libtool/libtool-1.4.3-r3.ebuild)
1077675574:  === (2 of 95) Compiling/Merging (sys-devel/libtool-1.4.3-r3::/usr/portage/sys-devel/libtool/libtool-1.4.3-r3.ebuild)
1077675703:  === (2 of 95) Post-Build Cleaning (sys-devel/libtool-1.4.3-r3::/usr/portage/sys-devel/libtool/libtool-1.4.3-r3.ebuild)
1077675705:  >>> AUTOCLEAN: sys-devel/libtool
1077675710: === Unmerging... (sys-devel/libtool-1.4.3-r1)
1077675721:  >>> unmerge success: sys-devel/libtool-1.4.3-r1
1077675726:  ::: completed emerge (2 of 95) sys-devel/libtool-1.4.3-r3 to /
1077675726:  >>> emerge (3 of 95) sys-libs/ncurses-5.3-r5 to /
1077675726:  === (3 of 95) Cleaning (sys-libs/ncurses-5.3-r5::/usr/portage/sys-libs/ncurses/ncurses-5.3-r5.ebuild)
1077675728:  === (3 of 95) Compiling/Merging (sys-libs/ncurses-5.3-r5::/usr/portage/sys-libs/ncurses/ncurses-5.3-r5.ebuild)
1077676204:  === (3 of 95) Post-Build Cleaning (sys-libs/ncurses-5.3-r5::/usr/portage/sys-libs/ncurses/ncurses-5.3-r5.ebuild)
1077676206:  >>> AUTOCLEAN: sys-libs/ncurses
1077676211: === Unmerging... (sys-libs/ncurses-5.3-r2)
1077676222:  >>> unmerge success: sys-libs/ncurses-5.3-r2
1077676226:  ::: completed emerge (3 of 95) sys-libs/ncurses-5.3-r5 to /
1077676226:  >>> emerge (4 of 95) sys-devel/m4-1.4-r1 to /
1077676226:  === (4 of 95) Cleaning (sys-devel/m4-1.4-r1::/usr/portage/sys-devel/m4/m4-1.4-r1.ebuild)
1077676228:  === (4 of 95) Compiling/Merging (sys-devel/m4-1.4-r1::/usr/portage/sys-devel/m4/m4-1.4-r1.ebuild)
1077676265:  === (4 of 95) Post-Build Cleaning (sys-devel/m4-1.4-r1::/usr/portage/sys-devel/m4/m4-1.4-r1.ebuild)
1077676267:  >>> AUTOCLEAN: sys-devel/m4
1077676272: === Unmerging... (sys-devel/m4-1.4)
1077676277:  >>> unmerge success: sys-devel/m4-1.4
1077676281:  ::: completed emerge (4 of 95) sys-devel/m4-1.4-r1 to /
1077676281:  >>> emerge (5 of 95) sys-devel/bison-1.875 to /
1077676281:  === (5 of 95) Cleaning (sys-devel/bison-1.875::/usr/portage/sys-devel/bison/bison-1.875.ebuild)
1077676283:  === (5 of 95) Compiling/Merging (sys-devel/bison-1.875::/usr/portage/sys-devel/bison/bison-1.875.ebuild)
1077676373:  === (5 of 95) Post-Build Cleaning (sys-devel/bison-1.875::/usr/portage/sys-devel/bison/bison-1.875.ebuild)
1077676375:  >>> AUTOCLEAN: sys-devel/bison
1077676380: === Unmerging... (sys-devel/bison-1.35)
1077676386:  >>> unmerge success: sys-devel/bison-1.35
1077676390:  ::: completed emerge (5 of 95) sys-devel/bison-1.875 to /
1077676390:  >>> emerge (6 of 95) sys-apps/groff-1.18.1-r4 to /
1077676390:  === (6 of 95) Cleaning (sys-apps/groff-1.18.1-r4::/usr/portage/sys-apps/groff/groff-1.18.1-r4.ebuild)
1077676392:  === (6 of 95) Compiling/Merging (sys-apps/groff-1.18.1-r4::/usr/portage/sys-apps/groff/groff-1.18.1-r4.ebuild)
1077676557:  === (6 of 95) Post-Build Cleaning (sys-apps/groff-1.18.1-r4::/usr/portage/sys-apps/groff/groff-1.18.1-r4.ebuild)
1077676559:  >>> AUTOCLEAN: sys-apps/groff
1077676564: === Unmerging... (sys-apps/groff-1.18.1-r3)
1077676569:  >>> unmerge success: sys-apps/groff-1.18.1-r3
1077676573:  ::: completed emerge (6 of 95) sys-apps/groff-1.18.1-r4 to /
1077676573:  >>> emerge (7 of 95) dev-libs/openssl-0.9.7c-r1 to /
1077676573:  === (7 of 95) Cleaning (dev-libs/openssl-0.9.7c-r1::/usr/portage/dev-libs/openssl/openssl-0.9.7c-r1.ebuild)
1077676575:  === (7 of 95) Compiling/Merging (dev-libs/openssl-0.9.7c-r1::/usr/portage/dev-libs/openssl/openssl-0.9.7c-r1.ebuild)
1077677398:  === (7 of 95) Post-Build Cleaning (dev-libs/openssl-0.9.7c-r1::/usr/portage/dev-libs/openssl/openssl-0.9.7c-r1.ebuild)
1077677400:  >>> AUTOCLEAN: dev-libs/openssl
1077677405: === Unmerging... (dev-libs/openssl-0.9.6k)
1077677421:  >>> unmerge success: dev-libs/openssl-0.9.6k
1077677425:  ::: completed emerge (7 of 95) dev-libs/openssl-0.9.7c-r1 to /
1077677425:  >>> emerge (8 of 95) dev-lang/python-2.3.3 to /
1077677425:  === (8 of 95) Cleaning (dev-lang/python-2.3.3::/usr/portage/dev-lang/python/python-2.3.3.ebuild)
1077677427:  === (8 of 95) Compiling/Merging (dev-lang/python-2.3.3::/usr/portage/dev-lang/python/python-2.3.3.ebuild)
1077677822:  === (8 of 95) Post-Build Cleaning (dev-lang/python-2.3.3::/usr/portage/dev-lang/python/python-2.3.3.ebuild)
1077677823:  >>> AUTOCLEAN: dev-lang/python
1077677823:  --- AUTOCLEAN: Nothing unmerged.
1077677823:  ::: completed emerge (8 of 95) dev-lang/python-2.3.3 to /
1077677823:  >>> emerge (9 of 95) dev-java/java-config-1.2.6 to /
1077677823:  === (9 of 95) Cleaning (dev-java/java-config-1.2.6::/usr/portage/dev-java/java-config/java-config-1.2.6.ebuild)
1077677824:  === (9 of 95) Compiling/Merging (dev-java/java-config-1.2.6::/usr/portage/dev-java/java-config/java-config-1.2.6.ebuild)
1077677832:  === (9 of 95) Post-Build Cleaning (dev-java/java-config-1.2.6::/usr/portage/dev-java/java-config/java-config-1.2.6.ebuild)
1077677833:  >>> AUTOCLEAN: dev-java/java-config
1077677833:  --- AUTOCLEAN: Nothing unmerged.
1077677833:  ::: completed emerge (9 of 95) dev-java/java-config-1.2.6 to /
1077677833:  >>> emerge (10 of 95) dev-java/sun-jdk-1.4.2.03 to /
1077677833:  === (10 of 95) Cleaning (dev-java/sun-jdk-1.4.2.03::/usr/portage/dev-java/sun-jdk/sun-jdk-1.4.2.03.ebuild)
1077677833:  === (10 of 95) Compiling/Merging (dev-java/sun-jdk-1.4.2.03::/usr/portage/dev-java/sun-jdk/sun-jdk-1.4.2.03.ebuild)
1077677834:  *** terminating.

As you can see it updated python to version 2.3.3. Since sun-jdk needs a file download emerge stopped at that point. I downloaded the sun-jdk file and restarted "emerge -u world" as I have done before a lot of times. But now emerge fails and prints the following:

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

Starting "phyton-updater" states:

Traceback (most recent call last):
  File "/usr/bin/portageq", line 9, in ?
    import portage,types,string
ImportError: No module named portage
Traceback (most recent call last):
  File "/usr/bin/portageq", line 9, in ?
    import portage,types,string
ImportError: No module named portage
 * Unable to proceed. Can not find PORTDIR. Make sure the command:
 *
 *   portageq portdir
 *
 * returns a value. If it doesn't, make sure you have updated to
 * latest portage version.
 *
 * Report bugs to http://bugs.gentoo.org/

Starting "portageq portdir" states:

Traceback (most recent call last):
  File "/usr/bin/portageq", line 9, in ?
    import portage,types,string
ImportError: No module named portage

Am I completely lost now? What can I do when emerge fails at that level?

best regards, Michael

Reproducible: Always
Steps to Reproduce:
1.emerge -u world
2.stop at sun-jdk, download file
3.emerge -u world

Actual Results:  
emerge fails to start completely

Expected Results:  
update system

sorry, not possible, emerge will not start anymore
Comment 1 SpanKY gentoo-dev 2004-02-25 09:16:27 UTC
*** Bug 42868 has been marked as a duplicate of this bug. ***
Comment 2 Chetan Sarva 2004-02-26 14:35:19 UTC
I have the same problem except that in my case I was able to complete the emerge world. All subsequent calls fail. I can link /usr/bin/python to python2.2 but I'm still unable to run python-updater.

 * Regenerating GNU info directory index...
 * Processed 220 info files.
 * IMPORTANT: 21 config files in /etc need updating.
 * Type emerge --help config to learn how to update config files.

root # etc-update
Traceback (most recent call last):
  File "/usr/lib/portage/bin/portageq", line 9, in ?
    import portage,types,string
  File "/usr/lib/portage/pym/portage.py", line 11, in ?
    import time,cPickle,atexit,grp,traceback,commands,pwd,cvstree,copy
AttributeError: 'module' object has no attribute '_extension_registry'
Traceback (most recent call last):
  File "/usr/lib/portage/bin/portageq", line 9, in ?
    import portage,types,string
  File "/usr/lib/portage/pym/portage.py", line 11, in ?
    import time,cPickle,atexit,grp,traceback,commands,pwd,cvstree,copy
AttributeError: 'module' object has no attribute '_extension_registry'
Scanning Configuration files...
Exiting: Nothing left to do; exiting. :)


# python-updater -o 2.2 -n 2.3 -p
Invalid or unset record 'packages' in mtimedb.
Invalid or unset record 'eclass' in mtimedb.
 * Starting Python Updater from 2.2 to 2.3 :
 * Searching for packages with files in /usr/lib/python2.2 ..
   Adding to list: dev-python/python-fchksum-1.6.1-r1
 * Calculating Upgrade Package List ..
 * Re-ordering packages to merge ..
Invalid or unset record 'packages' in mtimedb.
Invalid or unset record 'eclass' in mtimedb.
Traceback (most recent call last):
  File "/usr/portage/dev-lang/python/files/depreorder.py", line 25, in ?
    deps, slot = varapi.aux_get(pkg, ["DEPEND", "SLOT"])
TypeError: unpack non-sequence
 * Preparing to merge these packages in this order:
 * Python update completed successfully.
Comment 3 Michael Knappe 2004-03-21 03:39:44 UTC
Is there anything going on regarding our problem? Do you have any idea what we can do to solve it?
We are running a handful of Gentoo servers which have the same release state as this machine (fortunately as test system) had before we tried to run the update and we don't dare to update our production servers now.

Thank you for your help and best regards, Michael
Comment 4 Chetan Sarva 2004-03-21 11:09:18 UTC
Michael, here are a few things you can do to fix it. Unfortunately, I had the problem on 2 machines (home linux servers, nothing important) and only one of them is back to working order (the more important of the 2). that being said, I WAS able to successfully update a third machine without a problem.

- delete (move out of the way) /etc/portage/ if it exists. I had some package masks/unmasks there which seemed to be causing trouble. 
- comment out portage overlay in your make.conf. portage 2.5 may not like your modified/custom ebuilds
- use an emergency copy of portage. you can find one for your platform here:
/usr/portage/sys-apps/portage/files or at the URL mentioned in the readme. Make SURE you backup your make.conf before using any of those packages or else you will lose it!
- once you have a working emerge you should run python-updater to get all packages to use python 2.3x.

let me know if any of these suggestions helped.
Comment 5 Jason Stubbs (RETIRED) gentoo-dev 2004-04-08 22:40:14 UTC
If you machine is currently broken, grab a rescue tarball from http://dev.gentoo.org/~carpaski/portage_rescue/ and then untar it as follows:
tar xjpUvf portage-rescue-2.0.xxxx.tbz2 -C /

To ensure that your machine is updated without error:
emerge sync
emerge python portage
Comment 6 Michael Knappe 2004-04-09 00:55:27 UTC
Using an emergency copy of portage solved this problem. Thank you very much and best regards,

Michael