Just to clarify, the "quick fix" I posted here was supposed to help people to get rid of the buggy package. It doesn't fix the actual package.
Like I said before, the problem is not only the version number handling by pycentral but also the path of the installed files! If you have look at the package 0.7.97.1 for amd64 or 0.7.98 for i386 you'll see that files are put in /usr/lib/python3.1 In this package however files are put in /usr/lib/python3 instead which causes the problem you describe when simply changing the version number to 3.1. If you think pycentral should handle integer version numbers (at least it shouldn't exit with an error I guess) please file a bug report there. But to summarize for this package I think the files are put in the wrong place (compared with the package from testing and packages for i386) and the version number in the mentioned config file is wrong. If you want this package to work you'll have to extract it, rename the folder usr/lib/python3 to python3.1 and also change this path and the version number to 3.1 in usr/share/pyshared-data/python-apt. Then rebuild the package. But having a fixed version doesn't help you getting rid of the package from the system because dpkg won't remove it due to the prerm script which executes pycentral and fails. So the easiest thing to do is simply changing the 3rd line in /usr/share/pyshared-data/python-apt to "python-version = 2.6, 3.1, 2.5" and then you can replace the package. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org