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. >> 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. That's unlikely; reading the maintainer scripts shows that the only case where it moves it away is temporary and in the sequence: mv /etc/mailman/mm_cfg.py /etc/mailman/mm_cfg.py.old mv /etc/mailman/mm_cfg.py.new /etc/mailman/mm_cfg.py (It never "rms" it.) > 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. It is a configuration file, though. We have just found another RC bug in mailman: If the user removes it, it gets recreated with an automatically generated one: case "$1" in configure|abort-upgrade|abort-remove|abort-deconfigure) if [ ! -e /etc/$PACKAGE/mm_cfg.py ]; then echo "Configuring $PACKAGE for domain $DOMAIN ..." sed s/thunderchild.aszi.sztaki.hu/$DOMAIN/g /usr/lib/mailman/Mailman/mm_cfg.py.dist \ > /etc/$PACKAGE/mm_cfg.py fi ;; esac -- Lionel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]