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

[Lionel Elie Mamane]

On Thu, Nov 23, 2006 at 09:41:15PM +0100, Lionel Elie Mamane wrote:
> On Thu, Nov 23, 2006 at 03:55:15PM +0100, Raphael Hertzog wrote:
>> On Thu, 23 Nov 2006, Lionel Elie Mamane wrote:
>>>> I just checked, it is not a conffile.

>>> ... and not shipped by the package, but created by the postinst.

>>> Which means this also breaks _new_ installs as far as I understand it
>>> because if:

>> There's the possibility of not including the symlink in the package
>> but creating it at the same time when you create
>> /etc/mailman/mm_cfg.py.

> Yes, but if the admin removes the configuration file we are out of
> sync... I'll have to think a bit about a good solution. Thinking
> aloud... If I can keep that file from being compiled _at_ _all_, this
> would seem a good solution...

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.

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

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

-- 
Lionel