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.
But more importantly...
On 2026-03-03 16:08, Paul Tomblin via Mailman-users wrote:
So I went to submit a bug report to Debian about the fact that the mailman3-web
page drags in nginx for no reason. Turns out that the bug had been reported in
2021 and nobody who worked on it who understood mailman understood apache and
nobody who worked on it who understood apache understood mailman[1]. So I
submitted an update.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002795
... 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` / `virtualenv` installation method.
I would suggest, as such, that any other method including
distro-provided packages, should be discouraged in favor of doing it the
"pure python and pip" way. Note that it is VERY easy to actually use a
Python venv to run the entire Mailman suite, which I do in several
production instances.
Thomas
[1]: https://docs.mailman3.org/en/latest/install/install.html
_______________________________________________
Mailman-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
Archived at:
https://lists.mailman3.org/archives/list/[email protected]/message/LHYQB5A3FBNX2PLYQTC34PLBAPPSAYZX/
This message sent to [email protected]
