"pycentral rtinstall" script does not add symlinks for python2.6 on upgrade
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-central (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Jaunty |
Fix Released
|
High
|
Unassigned |
Bug Description
Binary package hint: python-central
After python2.6 gets installed and the rtinstall script is run for python-central, no symlinks are installed for packages that have the same version in intrepid and jaunty. I tested this with python-fstab in a chroot from intrepid->jaunty (and in a kvm upgrade tester). I will attach the full upgrade log with PYCENTRAL=debug.
Here are the revlevant lines:
...
Setting up python2.6-minimal (2.6.2~
pycentral: pycentral rtinstall --ignore-errors=yes python2.6
INFO: using unknown version '/usr/bin/
pycentral: 1 packages with Python-Version info installed, 0 for python2.6
...
If I run the same command ("pycentral rtinstall --ignore-errors=yes python2.6") after the upgrade the fstab symlinks get created.
Related branches
summary: |
- rtinstall script does not add symlinks for python2.6 + "pycentral rtinstall" script does not add symlinks for python2.6 |
summary: |
- "pycentral rtinstall" script does not add symlinks for python2.6 + "pycentral rtinstall" script does not add symlinks for python2.6 on + upgrade |
I think the problem is that rtinstall calls "requested_ versions( )" and that calls: versions( version_ only=True) python/ debian_ defaults are not listing python2.6 when
supported = supported_
so it runs into the problem that /usr/share/
the rtinstall script is run (because this file is part of python-minimal and at the intrepid version
when python2.6-minimal gets installed).
If we would reverse the logic to byte-compile everything that is not explictely unsupported that
would byte-compile python3.0 (with lots of failures) as well.