[Pkg-mailman-hackers] concurent bug reports?

GCS gcs-guest@users.alioth.debian.org
Mon, 15 Mar 2004 01:54:55 +0100


Hi Co-Maintainers,

I have found some questionable thing in bugrepors. See bug #232452 and
#235913 . The first says:
"
The following line in the default mm_cfg.py broke _all_ -owner email
aliases on my system, for all lists that were created with it:

MAILMAN_OWNER     = 'mailman-owner@%s' % DEFAULT_HOST_NAME

A look at Defaults.py reveals that by default, DEFAULT_HOST_NAME is
undefined. Per the documentation in Defualts.py, it has been replaced by
DEFAULT_EMAIL_HOST.

I verified that by making the change mentioned above, any newly created
lists work properly (i.e. the -ownder email aliases are not broken).
"

But the second states that:
"
As far as I can tell the MAILMAN_OWNER setting is completely ignored in
Mailman 2.1.4.  It's no longer mentioned in Defaults.py, having been
replaced by MAILMAN_SITE_LIST. (Here's the explaination given in the
CVS change log:
http://cvs.sourceforge.net/viewcvs.py/mailman/mailman/Mailman/Defaults.py.in?rev=2.28&view=markup
.)
"
And it's correct,
http://cvs.sourceforge.net/viewcvs.py/mailman/mailman/Mailman/Defaults.py.in?r1=text&tr1=2.28&r2=text&tr2=2.27&diff_format=h
shows that the complex MAILMAN_OWNER changed to contain the only the name
of site list in MAILMAN_SITE_LIST . So how could the user in the first
report successfully use MAILMAN_OWNER when it's not referenced anymore?
I think we should change that in mm_cfg.py , but note it will invalidate
Tollef's pending change for the first bug, also bug #232273 .

I wait for comments,
Laszlo/GCS