On Tue, Mar 3, 2026, at 4:42 PM, Thomas Ward wrote:
I would like to make a note. Firstly, the Debian bug reports *do not* always trickle upstream as they are not necessarily Mailman-upstream bugs or issues. Additionally, the Debian packaging is *NOT* done by Mailman's team necessarily, either, which introduces the "You need to deal with this in $DISTRO specifically, not with us" issue.
Yeah, i know, it's a packaging error, which is why I reported it to Debian, not to Mailman.
... if we read the Installation Instructions on the Mailman Suite documentation [1], we see that the "Recommended for Production" suggestion is to use the
pip/virtualenvinstallation method.
If you've got a fresh Debian install, and you see Debian packages for Mailman, that's what you're going to try first. Especially after having Mailman 2 installed from Debian packages from Debian 6 to Debian 11. It's only after encountering numerous problems that I uninstalled them and went to look at Mailman's documentation and do it the Mailman way.
It was a lot easier that way - for one thing the documentation is more up to date and complete.
-- Paul Tomblin