Bug#363016: release-notes: [sarge] Upgrade path for Mailman needs documenting
Package: release-notes
Severity: normal
The woody -> sarge upgrade path of mailman is a complete mess, and not
documented well enough during the upgrade itself. Please say something
about it in the release notes. Here's a possible text:
Issue 1: Administrator must update aliases
When using "MTA='Manual'", the administrator must update the aliases
needed for the lists manually. Run /var/lib/mailman/bin/genaliases to
see the new aliases you need.
Until you do that, some features will stop working and mails will go
out with an invalid Return-Path.
Issue 2: List passwords broken
List admin and moderator passwords are broken by this upgrade. Use
/var/lib/mailman/bin/change_pw to have new ones automatically
generated and emailed to the admins and moderators.
Issue 3: What to do when the queue is not empty
The instructions given when the queue is not empty at upgrade time are
incomplete and confusing. Better ones can be found at
http://lists.alioth.debian.org/pipermail/pkg-mailman-hackers/2006-April/000692.html
. (People reading this in another language than English are informed
that a translated version of this message is included in newer versions
of the package: Go to
http://packages.debian.org/testing/source/mailman, download the three
files linked to in the "Download mailman" section, run "dpkg-source -x
mailman_VERSION.dsc". The message is in the files
mailman-VERSION/debian/po/LANGUAGE.po.)
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-1-686
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Reply to: