mailman-3 was apparently added in 2017 and never gained any keywords. Given that -2 doesn't support py3, maybe it's time to keyword it?
Ping.
To give a quick status, I'm working on this. Unfortunately it's not that easy. The mailman package we had since 2017 had plenty of issues, both the packages itself and depepdencies that were broken. I seriously doubt anyone has ever used it. Mailman 3 is not just a new version, it's essentially a complete rewrite. The "mailman package" is just the backend, to replace mailman 2 it needs 2 fronend pieces (postorius and hyperkitty) that are poorly documented and each have a bunch of dependencies that also need to be packaged. By now the status is that the mailman package should work and its dependencies that had issues have been fixed. I have postorius packages that seem to work and after some more testing I will commit them as well. Hyperkitty (mail archives) still missing. If I have all of them I'll try to convert my major mailman installation and once I have it running for real I'll start re-adding keywords. I am aware of the need for a python 2 removal, though luckily mailman 2 doesn't have many dependencies, so I hope we can keep it for a bit more until we have the mailman 3 issues sorted out.
(In reply to Hanno Böck from comment #2) > To give a quick status, I'm working on this. > > Unfortunately it's not that easy. The mailman package we had since 2017 had > plenty of issues, both the packages itself and dependencies that were > broken. I seriously doubt anyone has ever used it. FYI I can verify I'm using it. :) I recall having to fix some permissions, but I don't think anything else. But yeah — Postorius, hyperkitty, gunicorn ... mailman3, from what I see on the MM3 list, has a lot of moving parts that all need to work together. A lot more complex than mailman2.
ping.
(In reply to Phil Stracchino (Unix Ronin) from comment #3) > (In reply to Hanno Böck from comment #2) > > To give a quick status, I'm working on this. > > > > Unfortunately it's not that easy. The mailman package we had since 2017 had > > plenty of issues, both the packages itself and dependencies that were > > broken. I seriously doubt anyone has ever used it. > > FYI I can verify I'm using it. :) I recall having to fix some permissions, > but I don't think anything else. I realize upon a further reading that I misunderstood Hanno's comment. You meant the Mailman *3* package from 2017, didn't you? I answered that while not thinking clearly about it. I'm using Mailman *2*, NOT *3*. My apologies for the confusion. For clarification: Mailman 3 is a completely different beast, I have not attempted to deploy it, and quite possibly will not deploy it because I'm not sure I actually have sufficient need for it any more to justify it.
Old versions last rited.
I am still using mailman and now I'm running into an issue. mailman-2 is last-rite'd and unavailable for rebuild/reinstall or updates. mailman-3 is not-yet stable, not even unmasked and by the package it is unclear if it actually pulls in postorius and hyperkitty or if they are still unavailable at all. What is the preferred way to go forward for users of mailman which are now stuck between a masked and soon-to-be removed package which actually works and a not-yet unmasked package which still lacks frontend support?
(In reply to Felix Tiede from comment #7) > I am still using mailman and now I'm running into an issue. > > mailman-2 is last-rite'd and unavailable for rebuild/reinstall or updates. > mailman-3 is not-yet stable, not even unmasked and by the package it is > unclear if it actually pulls in postorius and hyperkitty or if they are > still unavailable at all. > > What is the preferred way to go forward for users of mailman which are now > stuck between a masked and soon-to-be removed package which actually works > and a not-yet unmasked package which still lacks frontend support? There is some work going on in the lordvan overlay http://gpo.zugaina.org/net-mail/mailman
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=27f737c61dcf8a9273edbffd8c91625347069ef2 commit 27f737c61dcf8a9273edbffd8c91625347069ef2 Author: Michał Górny <mgorny@gentoo.org> AuthorDate: 2020-09-21 06:04:40 +0000 Commit: Michał Górny <mgorny@gentoo.org> CommitDate: 2020-09-21 06:07:21 +0000 net-mail/mailman: Remove last-rited <3 Bug: https://bugs.gentoo.org/710134 Signed-off-by: Michał Górny <mgorny@gentoo.org> net-mail/mailman/Manifest | 1 - net-mail/mailman/files/50_mailman.conf-r2 | 18 -- net-mail/mailman/files/README.gentoo-r3 | 181 --------------------- .../files/mailman-2.1.14_rc1-directory-check.patch | 19 --- net-mail/mailman/files/mailman-2.1.9-icons.patch | 12 -- net-mail/mailman/files/mailman.rc | 26 --- net-mail/mailman/files/mailman.service | 13 -- net-mail/mailman/mailman-2.1.33.ebuild | 169 ------------------- profiles/package.mask | 1 - 9 files changed, 440 deletions(-)
Status update: All mailman3-related packages should now be in the tree. I'm gonna ~-keyword the mailman3 ebuild soon, you'll also need hyperkitty and postorius to get something feature-comparable to mailman2. Unfortunately there is no easy migration path and the setup is quite involved. Please follow mailman's installation instructions. For people who might find this helpful: I created an overlay which allows you to go back to mailman2 in the meantime: https://github.com/hannob/mailman2-overlay However I want to warn that you should only consider this as an emergency solution for a short timeframe. It will likely break sooner or later with removal of more python2 infrastructure from the portage tree.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=095c9a044e88f77c92cebbffeaac12b31220dcb6 commit 095c9a044e88f77c92cebbffeaac12b31220dcb6 Author: Hanno Böck <hanno@gentoo.org> AuthorDate: 2020-11-10 09:53:14 +0000 Commit: Hanno Böck <hanno@gentoo.org> CommitDate: 2020-11-10 09:53:14 +0000 net-mail/mailman: Bump and ~amd64-keyword, Python 3.8 support Closes: https://bugs.gentoo.org/710134 Signed-off-by: Hanno Böck <hanno@gentoo.org> Package-Manager: Portage-3.0.9, Repoman-3.0.2 net-mail/mailman/Manifest | 1 + net-mail/mailman/mailman-3.3.2.ebuild | 43 +++++++++++++++++++++++++++++++++++ 2 files changed, 44 insertions(+)
