[Pkg-mailman-hackers] Bug#398771: installing mailman with python 2.3 causes loop condition during python upgrade

Raphael Hertzog hertzog at debian.org
Thu Nov 23 12:42:10 CET 2006


clone 398771 -1
reassign -1 python-support 0.5.5
retitle -1 python-support should warn and not fail when some files can't be byte-compiled
thanks

On Thu, 16 Nov 2006, Lionel Elie Mamane wrote:
> This bug, in my opinion, makes the package unsuitable for release with
> etch. It breaks upgrades from sarge to etch, if I understand well.

The bug is both in python-support and in mailman.

Python-support shouldn't fail when some files can't be byte-compiled but
just warn the user that something is not 100% normal. It looks like wrong
to make the installation of python2.4 fail when just one module is
kind of broken. Thus the clone and reassign.

> That file usually is a symlink to /etc/mailman/mm_cfg.py, a
> configuration file. I'm not terribly convinced it should be compiled
> at all, actually. It is a bug for it to be compiled unless it is
> *automatically* read from source when the source is newer than the
> compiled version. Any python expert could tell me whether it is the
> case?
> 
> Alex, you did have the file /etc/mailman/mm_cfg.py, right?

At least the file doesn't exist when python2.4 got installed. If the
mailman upgrade make the file disappear then this is the RC bug. But since
it's a configuration file, it might also be that the user removed it
manually and it doesn't get reinstalled because of dpkg's conffile
handling.

Unless someone comes up with evidence that the file gets removed during a
normal upgrade I don't think that this bug is RC. That said I haven't
tried the upgrade myself and someone should do that since the bug reporter
hasn't confirmed/denied yet. Alex ?

Cheers,
-- 
Raphaël Hertzog

Premier livre français sur Debian GNU/Linux :
http://www.ouaza.com/livre/admin-debian/




More information about the Pkg-mailman-hackers mailing list