For those of you out there running edgy that haven’t been able to find a solution to this:
Linking and byte-compiling packages for runtime python2.4…
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.4-minimal (–configure): subprocess post-installation script returned error exit status 1
then I have the answer! Just run:
sudo dpkg -P –force-all python2.4
sudo dpkg -P –force-all python-central
sudo apt-get -f install
Related posts:
#1 by beza1e1 on October 11, 2006 - 8:47 am
Well, that’s the crowbar …
#2 by dtlin on October 12, 2006 - 11:51 pm
I ran into this a week ago.
I think I did something along the lines of
apt-get install –reinstall $(dpkg -l $(apt-cache showpkg python-central | sed -n ‘s:,python-central.*::p’) | awk ‘/^ii/{print$2}’)
but I don’t exactly remember. Seems less… brutal.
#3 by Colin Watson on October 13, 2006 - 3:31 pm
Please don’t recommend –force-all to people. dpkg –force-help says that it “can seriously damage your installation” for a good reason.
#4 by JanC on October 18, 2006 - 8:00 pm
Another good reason not to use –force-* is that you destroy the information that the developers will need to fix the problem…
(I helped Matthias “doko” Klose today to find and fix several pycentral problems, and that wouldn’t have been possible if I would have done what you propose.)