pre-set PYTHONPATH breaks major upgrade
Bug #160805 reported by
Bob Lewis
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| update-manager (Ubuntu) |
Won't Fix
|
Wishlist
|
Rolf Leggewie | ||
Bug Description
Binary package hint: update-manager
This may actually be an underlying cause of several other bugs, but I'm not in a position to investigate, so...
The problem is that if you use update-manager to do an upgrade (in my case) from Gutsy to Hardy *and* you have PYTHONPATH set to use a library (even a local one) for the previous python version (2.5 in my case), necessary python modules will fail to load and the installation will break. Doing the installation with PYTHONPATH unset, everything works fine.
I might suggest the solution would be for update-manager to run python with the "-E" option to ignore any environment variable settings.
| Changed in update-manager: | |
| importance: | Undecided → Wishlist |
| status: | New → Confirmed |
| description: | updated |
Revision history for this message
| Rolf Leggewie (r0lf) wrote | #1 |
| tags: | removed: gutsy2hardy |
| tags: | added: gutsy2hardy |
| Changed in update-manager (Ubuntu): | |
| assignee: | nobody → Rolf Leggewie (r0lf) |
| status: | Confirmed → Incomplete |
Revision history for this message
| Rolf Leggewie (r0lf) wrote | #2 |
| Changed in update-manager (Ubuntu): | |
| status: | Incomplete → Won't Fix |
To post a comment you must log in.
This ticket is tagged gutsy2hardy, an upgrade path that is no longer supported. Is there still anything left that needs to be done in a later release?