Package: python-central
Version: 0.5.5
Severity: important
On the recent upgrade I've got
Linking and byte-compiling packages for runtime python2.3...
Traceback (most recent call last):
File "/usr/bin/pycentral", line 1325, in ?
main()
File "/usr/bin/pycentral", line 1319, in main
rv = action.run(global_options)
File "/usr/bin/pycentral", line 954, in run
requested = list(pyversions.requested_versions(vstring, version_only=True))
File "/usr/share/python/pyversions.py", line 113, in requested_versions
raise ValueError, 'empty set of versions'
ValueError: empty set of versions
dpkg: error processing python2.3 (--configure):
subprocess post-installation script returned error exit status 1
Since it fails, it forbids me from upgrading and many packages are
left in not configured state. Also such cruel exit doesn't provide any
insight on which package it really failed so I can't resolve the issue
by removing the "bad cow" package (if that is the issue of a bad
package). Please provide proper handling in such cases.
# pyversions -s
python2.3 python2.4
Thanks in advance
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (990, 'unstable'), (300, 'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-1-686
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages python-central depends on:
pn python <none> (no description available)
python-central recommends no packages.
-- no debconf information
--Yarik
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
