rtinstall scripts (to provide new 2.6 symlinks) are not run on intrepid->jaunty upgrade

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.

Hm, the patch is bogus. It looks like python-central.rtinstall is not run. It does not appear in the log. But if I run it manually:

root@top:/# pycentral rtinstall python2.6
pycentral: pycentral rtinstall python2.6
pycentral: 3 packages with Python-Version info installed, 3 for python2.6
pycentral: support python-fstab for python2.6
pycentral: reading /usr/share/pyshared-data/python-fstab
pycentral: Using python-version from pkgconfig: all
pycentral: install package python-fstab
pycentral: link shared files python2.6/python-fstab
pycentral: byte-compile files (2/2) python2.6
pycentral: ['/usr/lib/python2.6/dist-packages/fstab-1.3.egg-info', '/usr/lib/python2.6/dist-packages/fstab.py']
pycentral: support update-manager-core for python2.6
pycentral: reading /usr/share/pyshared-data/update-manager-core
pycentral: Using python-version from pkgconfig: 2.6, 2.5
pycentral: install package update-manager-core
pycentral: byte-compile files (49/49) python2.6
pycentral: ['/usr/lib/python2.6/dist-packages/DistUpgrade/DistUpgradeApport.py', '/usr/lib/python2.6/dist-packages/DistUpgrade/DistUpgradeAptCdrom.py', '...']
pycentral: byte-compile files (5/5) python2.6
pycentral: ['/usr/share/computerjanitor/plugins/deb_plugin.py', '/usr/share/computerjanitor/plugins/dpkg_status_plugin.py', '...']
pycentral: support python-apt for python2.6
pycentral: reading /usr/share/pyshared-data/python-apt
pycentral: Using python-version from pkgconfig: 2.6, 2.5
pycentral: install package python-apt
pycentral: byte-compile files (12/12) python2.6
pycentral: ['/usr/lib/python2.6/dist-packages/apt/__init__.py', '/usr/lib/python2.6/dist-packages/apt/cache.py', '...']
root@top:/# find /usr/lib/python* -name "fstab.py"
/usr/lib/python2.5/site-packages/fstab.py
/usr/lib/python2.6/dist-packages/fstab.py

It looks ok.

python-minimal gets unpacked in line 343 that provides the updated debian_defaults file.

The python2.6-minimal postinst is run in line 280:
...
Selecting previously deselected package python2.6-minimal.^M
(Reading database ... 12964 files and directories currently installed.)^M
Unpacking python2.6-minimal (from .../python2.6-minimal_2.6.1-1ubuntu7_amd64.deb) ...^M
Setting up python2.6-minimal (2.6.1-1ubuntu7) ...^M
^M

So it seems like the rtinstall postinst thinks that 2.6 is not a supported runtime and does not bytecompile.

This bug was fixed in the package python2.6 - 2.6.1-1ubuntu8

---------------
python2.6 (2.6.1-1ubuntu8) jaunty; urgency=low

  [Matthias Klose]
  * Update to 20090402, taken from the 2.6 release branch.
    - Fix issues #2625, #5068, #5387, #5536, #5561, #5619, #5632.
  * Address issues when working with PYTHONUSERBASE and non standard prefix
    (pointed out by Larry Hastings):
    - distutils.sysconfig.get_python_lib(): Only return ".../dist-packages" if
      prefix is the default prefix and if PYTHONUSERBASE is not set in the
      environment.
    - site.addusersitepackages(): Add USER_BASE/.../dist-packages to sys.path.
  * Do not add /usr/lib/pythonXY.zip on sys.path.

  [Marc Deslauriers]
  * debian/pyhtml2devhelp.py: update for python 2.6
  * debian/rules: re-enable documentation files for devhelp. LP: #338791.

  [Michael Vogt]
  * Fix missing rtinstall calls by inverting the supported/unsupported
    check. LP: #353251.

 -- Matthias Klose <email address hidden> Thu, 02 Apr 2009 17:34:21 +0200

This bug was fixed in the package python3.0 - 3.0.1-0ubuntu10

---------------
python3.0 (3.0.1-0ubuntu10) jaunty; urgency=low

  [Matthias Klose]
  * Update to 20090402 from the release30-maint branch.
  * Address issues when working with PYTHONUSERBASE and non standard prefix
    (pointed out by Larry Hastings):
    - distutils.sysconfig.get_python_lib(): Only return ".../dist-packages" if
      prefix is the default prefix and if PYTHONUSERBASE is not set in the
      environment.
    - site.addusersitepackages(): Add USER_BASE/.../dist-packages to sys.path.
  * Do not add /usr/lib/pythonXY.zip on sys.path.
  * Use the default python to build the htmldocs. LP: #348118.

  [Marc Deslauriers]
  * debian/pyhtml2devhelp.py: update for sphinx generated documentation.
  * debian/rules: re-enable documentation files for devhelp.

  [Michael Vogt]
  * Fix missing rtinstall calls by inverting the supported/unsupported
    check. LP: #353251.

 -- Matthias Klose <email address hidden> Thu, 02 Apr 2009 19:05:29 +0200

This fix seems to have caused the regression in bug 354251 (python3.0) and bug 354228 (python2.6).

The fix is wrong because it doesn't consider the case the the relevant runtime not being contained in *any* category in /usr/share/python/debian_defaults.

Before: supported-versions was used as a whitelist
After: unsupported-versions is used as a blacklist

The current behaviour of python-central is to die if asked to install a runtime which is neither supported nor old - that behaviour needs to be considered here.

I have a tangled system due to this bug. I tried to upgrade from intrepid from console using aptitude dist-upgrade and the upgrade is severely (?) hung. I would appreciate a "fix" for those of us with hung/broken systems, i.e. what sequence of commands will get python2.6 working so all of the packages and upgrade systems depending on it can get back on track. I ack that the most important fix for the ubuntu team is to get the packages cleaned up so this does not happen. But please also post here instructions on untangling a broken upgrade. Thanks.

Un-reopening, fixed by bug 354228.

I just ran into a interessting variant of this bug. It seems to be important in what order the packages get installed for them to be byte-compiled (done on a current jaunty chroot):

[chroot1]
# apt-get install python-distutils-extra
# apt-get install python2.4
# ls /usr/lib/python2.4/site-packages/
README

[chroot2]
# apt-get install python2.4
# apt-get install python-distutils-extra
# ls /usr/lib/python2.4/site-packages/
DistUtilsExtra README python_distutils_extra-0.90.egg-info

I think this will be fixed with the new python-central upload that fixes (#357884).

But there is still the inconsitency that the rtinstall scripts are not run when the new 2.4 runtime
gets installed (because of:
    if ! grep -sq '^supported-versions[^#]*python2.4' /usr/share/python/debian_defaults

But if a package gets (re)installed then pycentral creates the links for it. If its intentional, I find
it confusing :)

Closing the 2.5 task, that should be fine (its marked supported in both hardy and intrepid).

how do i fix it?

won't fix for python2.4