On Tue, Sep 27, 2022 at 04:04:41PM +0200, Neal Gompa wrote: > On Tue, Sep 27, 2022 at 3:20 PM Neal Gompa <ngompa13@xxxxxxxxx> wrote: > > > > On Tue, Sep 27, 2022 at 3:01 PM Stephen Smoogen <ssmoogen@xxxxxxxxxx> wrote: > > > > > > > > > > > > On Mon, 26 Sept 2022 at 17:56, Kevin Fenzi <kevin@xxxxxxxxx> wrote: > > >> > > >> Here's my thoughts on rhel9 upgrades. > > >> > > >> We have 188 RHEL7 or RHEL8 instances (counting both vm's and bare hardware). > > >> > > >> > > >> Some will just not move anytime soon: > > >> > > > > > > Is it possible to look at these as 'why does this need fedmsg?' 'what happens if it doesn't have fedmsg', and 'do we need it?' Sure, we can. But at this point I think we have already gotten rid of most of the things we really don't need. So, someone will need to make a compelling argument for dropping things (at least to me). > > > mailman01 is one where maybe not having it on fedmsg wouldn't be earth shattering > > > but it also has the bigger problem of all its libraries being FTBFS in Fedora and > > > being retired from there. At which point we go with 'do we need to run mailing lists?' Well, until we figure out how to otherwise handle the use cases that mailing lists handle now? For example: all the -sig groups in pagure have mailing lists that get all the bugs send to it. We would need to find another way to get bug content to those groups (and still keep it private). scm-commits is still important IMHO, because its a external record of changes. If someone messed with git history, that might be the only record of real changes. devel/test/a few other lists are still active. They would have to move to discourse or otherwise have something. So, needs a concrete plan. I am not at all in favor of 'turn it off' without moving all the needs. > > > > The mailman stack is FTBFS on Fedora right now because of a single > > library (python-aiosmtpd) not working properly because of changes in > > the SSL module in Python 3.10. The whole stack can branch into RHEL 9 > > just fine. > > And apparently that issue was fixed. Branching Mailman in EPEL9 is So, does that mean mailman3/hyperkitty/postorius can be fixed to not fail to build in Fedora now? That might be a bit less effort than them being retired and having to unretire them to fix them. > waiting on people adding infra-sig and epel-packagers-sig to > dependencies of the stack. > > See: https://bugzilla.redhat.com/show_bug.cgi?id=2030061 Yeah, django has been a holdup, but I think it just needs someone to say 'I will maintain this in epel9'. kevin
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx 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/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
