Your message dated Mon, 28 Nov 2005 21:55:26 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Your bug report about Mailman in Debian
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)
--------------------------------------
Received: (at submit) by bugs.debian.org; 23 Nov 2005 21:47:52 +0000
>From [EMAIL PROTECTED] Wed Nov 23 13:47:52 2005
Return-path: <[EMAIL PROTECTED]>
Received: from aragorn.weathertop.principate.org.uk ([217.147.92.65] ident=mail)
by spohr.debian.org with esmtp (Exim 4.50)
id 1Ef2T2-0005dr-00
for [EMAIL PROTECTED]; Wed, 23 Nov 2005 13:47:52 -0800
Received: from matthew by aragorn.weathertop.principate.org.uk with local (Exim
3.36 #1 (Debian))
id 1Ef2Sz-0000Ja-00; Wed, 23 Nov 2005 21:47:49 +0000
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Matthew Vernon <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: mailman: Upgrade does not warn that new aliases are required
X-Mailer: reportbug 3.8
Date: Wed, 23 Nov 2005 21:47:49 +0000
Message-Id: <[EMAIL PROTECTED]>
Sender: Matthew Vernon <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2005_01_02
Package: mailman
Version: 2.1.5-8
Severity: grave
Justification: renders package unusable
Hi,
Prior to the woody->sarge upgrade, a mailing list aliasfile entry
looked like:
foundation: "|/var/lib/mailman/mail/wrapper post foundation"
foundation-admin: "|/var/lib/mailman/mail/wrapper mailowner foundation"
foundation-request: "|/var/lib/mailman/mail/wrapper mailcmd foundation"
foundation-owner: foundation-admin
Now it has to look like:
foundation: "|/var/lib/foundation/mail/mailman post foundation"
foundation-admin: "|/var/lib/foundation/mail/mailman admin foundation"
foundation-bounces: "|/var/lib/foundation/mail/mailman bounces
foundation"
foundation-confirm: "|/var/lib/foundation/mail/mailman confirm
foundation"
foundation-join: "|/var/lib/foundation/mail/mailman join foundation"
foundation-leave: "|/var/lib/foundation/mail/mailman leave foundation"
foundation-owner: "|/var/lib/foundation/mail/mailman owner foundation"
foundation-request: "|/var/lib/foundation/mail/mailman request
foundation"
foundation-subscribe: "|/var/lib/foundation/mail/mailman subscribe
foundation"
foundation-unsubscribe: "|/var/lib/foundation/mail/mailman unsubscribe
foundation"
The upgrade doesn't warn you that your mailing lists will stop working
properly, not does it attempt to edit your /etc/aliases file to make
them start working. The latter would be ideal, the former is clearly
essential - an upgrade shouldn't break the entire package wihout
warning!
Regards,
Matthew
-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.4.25
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages mailman depends on:
ii apache [httpd] 1.3.33-6sarge1 versatile, high-performance HTTP s
ii apache-ssl [httpd] 1.3.33-6sarge1 versatile, high-performance HTTP s
ii cron 3.0pl1-86 management of regular background p
ii debconf 1.4.30.13 Debian configuration management sy
ii exim [mail-transport-agen 3.36-16 An MTA (Mail Transport Agent)
ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an
ii logrotate 3.7-5 Log rotation utility
ii pwgen 2.03-1 Automatic Password generation
ii python 2.3.5-2 An interactive high-level object-o
ii ucf 1.17 Update Configuration File: preserv
-- debconf information:
* mailman/site_languages: en
* mailman/used_languages: en
* mailman/create_site_list:
mailman/queue_files_present:
* mailman/default_server_language: en
* mailman/gate_news: false
---------------------------------------
Received: (at 340503-done) by bugs.debian.org; 28 Nov 2005 20:55:27 +0000
>From [EMAIL PROTECTED] Mon Nov 28 12:55:27 2005
Return-path: <[EMAIL PROTECTED]>
Received: from 213-84-114-29.adsl.xs4all.nl ([213.84.114.29]
helo=capsaicin.mamane.lu)
by spohr.debian.org with esmtp (Exim 4.50)
id 1Egq23-0006OO-G1
for [EMAIL PROTECTED]; Mon, 28 Nov 2005 12:55:27 -0800
Received: from master by capsaicin.mamane.lu with local (Exim 4.54)
id 1Egq22-0000rW-78
for [EMAIL PROTECTED]; Mon, 28 Nov 2005 21:55:26 +0100
Date: Mon, 28 Nov 2005 21:55:26 +0100
From: Lionel Elie Mamane <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Your bug report about Mailman in Debian
Message-ID: <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Operating-System: GNU/Linux
X-Request-PGP: http://www.mamane.lu/openpgp/rsa_v4_4096.asc
User-Agent: Mutt/1.5.11
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-1.0 required=4.0 tests=BAYES_00,YOUTHERE
autolearn=no version=2.60-bugs.debian.org_2005_01_02
Hi,
In response to your bug report on mailman in Debian:
http://bugs.debian.org/340503 .
> You were saying:
> Prior to the woody->sarge upgrade, a mailing list aliasfile entry
> looked like:
> foundation: "|/var/lib/mailman/mail/wrapper post foundation"
> Now it has to look like:
> foundation: "|/var/lib/foundation/mail/mailman post foundation"
^^^^^^^^^^
Certainly not. It has to be "mailman" there, we don't create a
directory in /var/lib for each list.
Besides, there is a symlink in /var/lib/mailman/mail from wrapper to
mailman, so the old alias file entries will just work, won't it? Or am
I completely confused?
--
Lionel
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
