pycompile fixes needed for maverick
Bug #689615 reported by
Matthias Klose
This bug affects 7 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-defaults (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Maverick |
Fix Released
|
High
|
Unassigned | ||
python2.7 (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Maverick |
Invalid
|
Undecided
|
Unassigned | ||
update-manager (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Maverick |
Invalid
|
Undecided
|
Unassigned |
Bug Description
some pycompile backports are needed to allow smooth maverick -> natty upgrades. This changes are conservative, and the same that are already in Debian squeeze or considered for it.
some of the failing upgrade reports are: 687658, 688846, 688965, 689103, 689306
the changes are limited to pycompile, only used by a few packages built by dh_python2
Changed in python2.7 (Ubuntu): | |
importance: | Undecided → High |
Changed in python2.7 (Ubuntu): | |
status: | New → Fix Released |
To post a comment you must log in.
Is there any chance we could at least mitigate this in the natty preinst as well? We can't really guarantee that everyone installs maverick-updates before upgrading to natty.
Also, is this a bug in natty itself? If not, please close the natty task.