On 25/09/2022 20.54, Kevin Fenzi wrote:
On Fri, Sep 23, 2022 at 03:55:47PM +0200, Sjoerd Mullender wrote:
> What's the deal with maintaining mailing lists on Fedora these days?
>
> For years I've used mailman (first mailman2, now mailman3) on Fedora to
> administer mailing lists. In mailman3, you also need postorius to provide a
> web interface to users and hyperkitty to provide mail archive support.
>
> On Fedora 35, mailman2 isn't available anymore, so that's when I switched to
> mailman3. The original Fedora 35 did not have postorius, but that became
> available later. Hyperkitty on the other hand is not available on fedora
> 35. I use an rpm that I built myself.
>
> On Fedora 36, mailman3 can be installed, but both postorius and hyperkitty
> (there it is in the repository) cannot. They both depend on a too old
> version of django.
>
> On Fedora 37 (I know, not released yet, so any complaints should go to the
> testing list) none of the packages can be installed since they all depend on
> python 3.10 and F37 will come with 3.11. The packages are actually the
> unmodified F36 packages.
>
> Do people use mailman3 on Fedora? If so, how?
Sadly those packages are difficult to keep working and they have fallen
behind. :( I'm sure the maintainers would welcome help though if you can
work on them or help test fixes.
>
> Should I invest time in getting it to work in a python virtual environment?
> And how would that work with SELinux?
Well, up to you, but it would be nice to contibute to the packages and
get them working again.
> This very mailing list (users(a)lists.fedoraproject.org) is managed with
> mailman3, but does the system on which it runs run Fedora?
Nope, it's running on a RHEL7 vm. ;(
We would very much like to move it to a newer version however, and
if the Fedora version became available/working again we could look at
that.
kevin
I bit the bullet and took the challenge.
I have created RPMs for mailman3, hyperkitty, and postorius and got them
to work on Fedora 36. (Fedora 37 is a bridge too far at the moment
because it uses Python 3.11. This information is of course irrelevant
for this list at this time ;-) ).
To get it to work, I had to update a lot of other RPMs as well. This is
the complete list:
hyperkitty-1.3.5.9-1.fc36.noarch.rpm
hyperkitty-doc-1.3.5.9-1.fc36.noarch.rpm
mailman3-3.3.5-0.1.fc36.noarch.rpm
postorius-1.3.6.9-1.fc36.noarch.rpm
python-django-haystack-docs-3.2.1-0.fc36.noarch.rpm
python-rjsmin-docs-1.2.0-0.fc36.x86_64.rpm
python3-django-compressor-4.1-0.fc36.noarch.rpm
python3-django-haystack-3.2.1-0.fc36.noarch.rpm
python3-django-mailman3-1.3.7.9-1.fc36.noarch.rpm
python3-flufl-bounce-4.0-0.fc36.noarch.rpm
python3-flufl-i18n-3.2-0.fc36.noarch.rpm
python3-flufl-lock-5.1-0.1.fc36.noarch.rpm
python3-mailman-hyperkitty-1.2.1-0.1.fc36.noarch.rpm
python3-mailmanclient-3.3.3-2.fc36.noarch.rpm
python3-mailmanclient-3.3.3-4.fc36.noarch.rpm
python3-mistune-2.0.4-0.fc36.noarch.rpm
python3-rcssmin-1.1.0-0.fc36.x86_64.rpm
python3-rjsmin-1.2.0-0.fc36.x86_64.rpm
All of these are based on the Fedora 36 source RPMs, but with updated
sources and the occasional change in the patches used. The hyperkitty
and postorius versions are not based on official releases but just the
latest sources.
I think perhaps the most problematic change is the update to the
python3-mistune package. F36 comes with 0.8.4 but mailman requires 2.0,
and that's an incompatible rewrite if I understand correctly.
Since I have done minimal testing (one system, a single mailing list
with one subscriber) it may not be ready for prime time yet.
Question is, how to proceed? Since there are so many updated packages,
who can I contact?
--
Sjoerd Mullender