Summary: | site-packages directory is incompletely populated after upgrade to Python 2.3 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Jeff Stearns <jps-dilbert> |
Component: | Current packages | Assignee: | Python Gentoo Team <python> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Jeff Stearns
2004-02-23 01:32:42 UTC
did you run the python package updater like the post-install output said to ? I can't say for sure whether I ran the updater or not. I take notes during the install, and this step isn't listed, so I assume that I didn't do it. As a rule, I do everything that emerge post-install scripts recommend, but I suspect that some post-install output slips past me unnoticed. (This can easily happen whenever emerge updates more than one package; it emits the post-install output but then continues onward spitting out the output from the next package being built. Under these conditions, it's easy to miss important post-install messages buried among thousands of lines from makefiles and install scripts.) Since it's safe to run python-updater multiple times, I ran it just now. Nothing changed. :-( 2004/02/23 20:44:27 - Starting Python Updater from 2.2 to 2.3 : 2004/02/23 20:44:27 - Searching for packages with files in /usr/lib/python2.2 .. 2004/02/23 20:44:30 - Calculating Upgrade Package List .. 2004/02/23 20:44:30 - Re-ordering packages to merge .. 2004/02/23 20:44:30 - Preparing to merge these packages in this order: 2004/02/23 20:44:30 - Python update completed successfully. not a bug, all those files are portage's things and they've been moved to /usr/lib/portage/pym i remember portage's ebuild trying to clean those files, but in theory they don't affect anything since any recent version of portage will be using python2.3 and not touch the python2.2 files. |