Bug 225543 - [NEW PORT] mail/mailman3: GNU Mailman 3.3.1, core
Summary: [NEW PORT] mail/mailman3: GNU Mailman 3.3.1, core
Status: Open
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Many People
Assignee: Kurt Jaeger
URL: https://reviews.freebsd.org/D14126
Keywords: feature, needs-qa
Depends on: 224993 225010 230164
  Show dependency treegraph
Reported: 2018-01-29 20:14 UTC by Charlie Li
Modified: 2020-05-24 19:14 UTC (History)
15 users (show)

See Also:

mail/mailman3 (13.26 KB, patch)
2018-01-29 20:14 UTC, Charlie Li
no flags Details | Diff
svn-diff for 3.3.1 (18.37 KB, patch)
2020-05-24 19:13 UTC, Kurt Jaeger
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Charlie Li 2018-01-29 20:14:01 UTC
Created attachment 190170 [details]

Initial submission of GNU Mailman 3 into the ports tree. See review D14126.
Comment 1 Charlie Li 2018-01-31 19:57:46 UTC
Comment on attachment 190170 [details]

See Phabricator for updated patch.
Comment 2 Kurt Jaeger freebsd_committer 2018-07-29 19:37:36 UTC
Now that the zope dependency has hit the tree, will you update this to 3.2 ?
Comment 3 Charlie Li 2018-07-29 19:42:27 UTC
(In reply to Kurt Jaeger from comment #2)
I have 3.2 built locally with updated port files and such. Still need to do runtime testing.

Furthermore, there is a hard dependency on databases/py-sqlalchemy12, but another hard dependency databases/py-alembic specifies databases/py-sqlalchemy10. I locally patched databases/py-alembic to use databases/py-sqlalchemy12 to facilitate building and runtime testing, but anything further is a topic for another PR.
Comment 4 Charlie Li 2018-07-31 20:59:39 UTC
Phabricator review D14126 refreshed, updated to 3.2.0, with inline questions. Still QAing runtime on my end but the port-plumbing should be somewhat sane now.
Comment 5 Daniel Winter 2019-04-09 12:27:53 UTC

What is the state of this port? It is not yet in the official ports tree.
I would prefer to have a port instead of installing it with Ansible from the Git sources.
Can I help somehow with the process? What would be needed?
Comment 6 Charlie Li 2019-04-09 13:30:36 UTC
(In reply to Daniel Winter from comment #5)
I have an update to 3.2.2 waiting in the wings in my local ports repo. As with the initial 3.2.0 efforts, paths need to be checked, and patched if necessary, to follow our hier(7) as upstream hardcodes many paths to the Linux layout (and USES=pathfix won't automatically get them). Other than that, I still need to test runtime itself.
Comment 7 Matthias Andree freebsd_committer 2019-09-07 11:13:51 UTC
Comment 8 Matthias Andree freebsd_committer 2019-09-07 11:14:44 UTC
Charlie, what's the state of your efforts from comment #6?
Comment 9 Eirik Oeverby 2019-12-27 13:53:37 UTC
Now that python2 is EOL, having mailman3 in ports becomes critical. Is there a way to bump the priority of this, perhaps someone can take it upon themselves to finish the port? Or are "nobody" using mailman these days?
Comment 10 Kurt Jaeger freebsd_committer 2020-01-05 16:05:27 UTC
testbuild with the most recent version from the review, updated to 3.3.0, builds fine.

TODO: more run-tests, path fixes as requested in the review.
Comment 11 Julien Cigar 2020-02-11 13:31:00 UTC
any updates on this? I'm eagerly waiting for this port to upgrade our Mailman instances here ... thanks :-)
Comment 12 Kurt Jaeger freebsd_committer 2020-02-12 07:21:18 UTC
(In reply to Julien Cigar from comment #11)
No updates, we still need run-tests.
Comment 13 Antonio Huete Jimenez 2020-03-25 01:51:58 UTC
I would also like to see this in ports. anything I can help with?
Comment 14 Kurt Jaeger freebsd_committer 2020-05-24 19:13:50 UTC
Created attachment 214820 [details]
svn-diff for 3.3.1

testbuilds look fine, run-tests still needed.