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

Raphael Hertzog hertzog at debian.org
Fri Nov 24 08:18:59 CET 2006


On Fri, 24 Nov 2006, Lionel Elie Mamane wrote:
> Ah, I think I have it. We can remove the symlink in pre-rtupdate and
> put it back in post-rtupdate. That takes care of python version
> updates. Now, for new installs... Python will guaranteed be configured
> before us, so indeed creating the symlink in postinst will be safe.

This looks like really overkill for your need. Python-support has been
fixed and will only warn about the failed byte-compilation, so mailman's
installation shouldn't fail anymore.

> > The file is small (just configuration), so having it not compiled is
> > perfectly acceptable performance-wise...

python-support doesn't allow you to do that. python-central IIRC has an
exclusion mechanism but I don't think that you can leverage it with the
standard debhelper substitution.

> Not only that, but more often than not the compiled version will be
> useless/outdated as the admin will have edited the config file.

python is smart, it only uses the byte-compiled file it it's newer than
the .py file. So it's not a problem.

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