[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 01:22:35PM +0100, Lionel Elie Mamane wrote:
> On Thu, Nov 23, 2006 at 12:42:10PM +0100, Raphael Hertzog wrote:
>> On Thu, 16 Nov 2006, Lionel Elie Mamane wrote:

>>> 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.

>> 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.

> 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:

 - mailman gets unpacked _before_

 - python2.4 gets configured _before_

 - mailman gets configured

That last bit _will_ tend to happen since dpkg tries to configure
dependencies before the package itself. The first bit may or may not
happen.


That's also harder to fix from mailman's side, if possible at all.

-- 
Lionel