Package: python-central
Version: 0.5.1
Severity: grave
I originally reported this at [0]; this is just a copy/paste of that
email (with an updated version of the error message). I mentioned there
that I thought it was grave (it prevents python from installing), and I
got no responses either way, so that's how I'm reporting it.
When installing a package that uses pycentral, that I had previously
installed by hand, I got an error:
Setting up python2.3 (2.3.5-15) ...
byte-compiling files for package python2.3...
Linking and byte-compiling packages for runtime python2.3...
pycentral: pycentral rtinstall: package python-mutagen: already exists:
/usr/lib/python2.3/site-packages/mutagen/__init__.py
pycentral rtinstall: package python-mutagen: already exists:
/usr/lib/python2.3/site-packages/mutagen/__init__.py
dpkg: error processing python2.3 (--configure):
subprocess post-installation script returned error exit status 1
I think making this an error is a bad decision. File conflicts within
the packaging system should already be dealt with via dpkg. Outside of
the package system, dpkg always silently overwrites local
non-configuration files, and it's not an error normally.
This is particularly bad for Python, because the default install prefix
for local software is /usr, and there's no distutils uninstall command.
So you have to manually find and remove all the files from any
locally-installed package to switch to dpkg's version.
Unless there's a good reason for this behavior, I think this is a grave
bug for pycentral, since no other part of the packaging system creates
errors in this situation.
[0] http://lists.debian.org/debian-python/2006/06/msg00292.html
--
Joe Wreschnig [EMAIL PROTECTED]
signature.asc
Description: This is a digitally signed message part
