rtinstall scripts (to provide new 2.6 symlinks) are not run on intrepid->jaunty upgrade
Bug #353251 reported by
Michael Vogt
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python2.4 (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned | ||
Jaunty |
Won't Fix
|
Undecided
|
Unassigned | ||
python2.5 (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Jaunty |
Fix Released
|
Undecided
|
Unassigned | ||
python2.6 (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Jaunty |
Fix Released
|
High
|
Unassigned | ||
python3.0 (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Jaunty |
Fix Released
|
High
|
Unassigned |
Bug Description
Binary package hint: python-central
When installing python-fstab in a intrepid chroot and upgrading to jaunty the symlinks for python-fstab do not get updated for the python2.6 runtime. This means that:
$ python -c 'import fstab'
fail. This potentially affects more packages but I can confirm it with python-fstab. Attach is a debug log (with PYCENTRAL=debug). Here is a excerpt:
...
Setting up python2.6 (2.6.1-1ubuntu7) ...
Setting up python (2.6.1-0ubuntu9) ...
pycentral: pycentral updatedefault python2.5 python2.6
pycentral: update default: update 0 packages for python2.6
Setting up python-central (0.6.11ubuntu5) ...
...
summary: |
- does not provide 2.6 symlinks for python-fstab (and others?) when - python2.6 gets installed + rtinstall scripts (to provide new 2.6 symlinks) are not run on + intrepid->jaunty upgrade |
affects: | python-central (Ubuntu Jaunty) → python2.6 (Ubuntu Jaunty) |
Changed in python3.0 (Ubuntu Jaunty): | |
importance: | Undecided → High |
status: | New → In Progress |
Changed in python2.6 (Ubuntu Jaunty): | |
status: | New → In Progress |
To post a comment you must log in.
It looks like the reason is that python-fstab is not touched (intrepid and jaunty version are the same) during the upgrade. This may also happen if a python package gets upgraded before the new runtime is unpacked I suspect.