[CCed debian-python] On Mi, 2010-09-29 at 14:31 +0200, Stefan Fleischmann wrote: > 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. AFAIK, /usr/lib/python3 is the new location.
Dear debian-python subscribers, could someone please propose a fix for python-apt? I do not intent to drop Python 3 support, but considering that there is a new RC bug each month because python3 packaging changes I start to wonder whether this is worth the effort. Python maintainers: Breaking backward compatibility in unstable is not nice, especially not every (second) month. You should have thought about it while python3 was still in experimental, not afterwards. -- Julian Andres Klode - Debian Developer, Ubuntu Member See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/. -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1285765930.341.9.ca...@jak-thinkpad
