Your message dated Mon, 27 Nov 2006 08:11:36 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#400010: mailman: Fails to respect admin deletion of
configuration file
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: mailman
Version: 1:2.1.9-1
Severity: serious
Justification: Etch RC policy: 3 - last paragraph
Quoting Etch RC policy:
> Changes to configuration files must be preserved during a package
> upgrade. Configurations must be preserved on package removal, and
> only deleted when the package is purged.
But a deleted /etc/mailman/mm_cfg.py gets recreated automatically the
next time the postinst script is run in any way:
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
This is further complicated by the fact that a missing
/etc/mailman/mm_cfg.py makes the new-pyton-policy-mandated bytecode
compile fail. We should probably not ship the symlink from
/var/lib/mailman/Mailman/mm_cfg.py to /etc/mailman/mm_cfg.py in the
package, but handle it manually in sync with the file itself.
--
Lionel
--- End Message ---
--- Begin Message ---
On Sun, Nov 26, 2006 at 08:51:00PM -0800, Steve Langasek wrote:
> On Thu, Nov 23, 2006 at 02:12:51PM +0100, Lionel Elie Mamane wrote:
>>> Changes to configuration files must be preserved during a
>>> package upgrade. Configurations must be preserved on package
>>> removal, and only deleted when the package is purged.
>> But a deleted /etc/mailman/mm_cfg.py gets recreated automatically the
>> next time the postinst script is run in any way:
> FWIW, I'm not sure that this qualifies as RC under this policy. It
> depends entirely on whether removing the config file qualifies as a
> valid configuration change, IMHO. Does mailman run when this file
> is missing?
No, mailman doesn't run when this file is missing. Closing bug then.
--
Lionel
--- End Message ---
