On Mon, 5 Sept 2022 at 03:13, Matthias Runge <[email protected]>
wrote:
> On 02/09/2022 22:10, Stephen Smoogen wrote:
>
> > This lowered the long term load average but now led to reports where the
> > mailman REST daemon does not respond in time due to timeouts. Looking at
> > what is going on in the logs, and reading through the forums, my guess
> > was these are issues due to the old django and early mailman we are
> using.
> >
> > At this point I started to look at what would be needed to update
> > mailman to a newer version which could be supported on Fedora or RHEL9.
> > The main issues are setting up the django "project" and then making sure
> > that the needed packages are available. The upstream 'recommended' ways
> > are to use either venv or containers but I found that the solutions are
> > for a) docker, b) have a lot of security vulnerabilities in the quay
> > listing and c) using it looks like Debian/Ubuntu packages. There is also
> > a lot of customization needed to the point it might be best to start
> > from scratch on that.
> >
> > I am thinking it might make better sense to work out a project and
> > layout in staging, get a copy of the database from db01 and try
> > experiments to make it work until we either burn it all down or not.
> >
>
>
> I'd be curious on the django version and release issues. The way the
> project is working (regular releases, release often,...) and getting
> long term support does not really work well with a community-based
> approach ("the community will keep the version alive", "do backports",
> etc) with epel packages.
>
>
I forgot to answer you on this. These are the versions being used.
django-assets-0.8-1.el7.centos.noarch
hyperkitty-1.1.5-0.1.el7.centos.noarch
hyperkitty-selinux-1.1.5-0.1.el7.centos.noarch
mailman3-3.1.1-0.6.el7.centos.noarch
mailman3-fedmsg-plugin-0.5-6.el7.noarch
mailman3-hyperkitty-1.1.1-0.2.el7.centos.noarch
mailman3-selinux-3.1.1-0.6.el7.centos.noarch
python-django-1.8.8-2.el7.centos.noarch
python-django-allauth-0.34.0-1.el7.centos.noarch
python-django-appconf-1.0.2-1.el7.centos.noarch
python-django-bash-completion-1.8.8-2.el7.centos.noarch
python-django-browserid-2.0.2-1.el7.centos.noarch
python-django-compressor-2.0-1.el7.centos.noarch
python-django-extensions-1.6.1-1.el7.centos.noarch
python-django-gravatar2-1.0.6-2.el7.centos.noarch
python-django-haystack-2.5.0-1.el7.centos.noarch
python-django-haystack-xapian-2.0.0-2.el7.centos.noarch
python-django-mailman3-1.1.1-0.3.el7.centos.noarch
python-django-paintstore-0.2-1.el7.centos.noarch
python-django-picklefield-0.3.2-1.el7.centos.noarch
python-django-q-0.7.18-1.el7.centos.noarch
python-django-rest-framework-3.3.3-1.el7.centos.noarch
> While there is a bug https://bugzilla.redhat.com/show_bug.cgi?id=2033064
> to get django in EPEL, I'm not sure how much this would help you here?
>
> Would be hosting on Fedora an alternative?
>
> Matthias
> _______________________________________________
> infrastructure mailing list -- [email protected]
> To unsubscribe send an email to
> [email protected]
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/[email protected]
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
>
--
Stephen Smoogen, Red Hat Automotive
Let us be kind to one another, for most of us are fighting a hard battle.
-- Ian MacClaren
_______________________________________________
infrastructure mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
