clone 384094 -1
reassign -1 python2.5-minimal 2.5-3
retitle -1 Python2.5 fails to install with python-minimal 2.4.3-11 from etch
severity 384094 important
retitle 384094 python-central: inconsistent handling of list of installed 
runtimes
found 384094 0.5.10
thanks

On Wed, 15 Nov 2006, Igor Goryachev wrote:
> Setting up python2.5-minimal (2.5-3) ...
> Linking and byte-compiling packages for runtime python2.5...
> pycentral: pycentral rtinstall: installed runtime python2.5 not found
> pycentral rtinstall: installed runtime python2.5 not found

The problem is not with python-central itself but with the version of
python-minimal that is used in combination.

The problem can only be reproduced in etch which has python-minimal
2.4.3-11. The version 2.4.4-1 from sid has an updated
/usr/share/python/debian_defaults which knows python2.5:
$ cat /usr/share/python/debian_defaults
[DEFAULT]
# the default python version
default-version = python2.4
# all supported python versions
supported-versions = python2.4
# formerly supported python versions
old-versions = python2.3
# unsupported versions, including older versions
unsupported-versions = python2.3, python2.5

Whereas etch doesn't:
$ cat /usr/share/python/debian_defaults
[DEFAULT]
# the default python version
default-version = python2.4
# all supported python versions
supported-versions = python2.3, python2.4
# formerly supported python versions
#old-versions = python2.3

So the proper fix is to make sure that a good version of python-minimal is
setup before the install of python2.5. So the bug is in python2.5-minimal
and I'm reassigning it.

Apart from that, python-central still does very weird things in the way it
handles the list of supported runtimes.

The function get_supported_runtimes() has been modified to accept a
parameter "with_unsupported" which defaults to True and it's only used
with explicit assignation to "True". So I believe the default value should
have been false. However the action "RuntimeInstall" calls the function
without indicating with_unsupported=True which means that if the default
value is changed to False, this failure will happen again even if the
good version of python-minimal is installed.

        for rt in get_installed_runtimes():
            if rt.name == self.rtname:
                self.runtime = rt
                break
        if not self.runtime:
            self.error('installed runtime %s not found' % self.rtname)

I'll prepare an NMU of python 2.5 to fix the RC problem. And I'm downgrading
this bug so that this inconsistent handling of installed runtimes can be fixed
later.

Cheers,
-- 
Raphaël Hertzog

Premier livre français sur Debian GNU/Linux :
http://www.ouaza.com/livre/admin-debian/

Reply via email to