On Mon, Jul 6, 2026 at 11:05 PM Adam Williamson <[email protected]> wrote: > > Hi folks! > > I want to formally propose an idea that has been kicked around a bit > informally lately: gating all stable release updates on the relatively > new rmdepcheck reverse dependency static checker. This would include > Fedora and EPEL updates.
... you have my bow! ... and my axe! In general I think this is a good idea, and I would also think it would be a good idea for rawhide and branched. Failures could always be waived, and in case of "soname bump rebuild that is incomplete because something doesn't build" that would be a perfectly good reason to do so - and it would make it explicit that the packager who waived the failures took responsibility for that breakage - and provide documentation for it alongside the update. That said, stable releases and EPEL is likely less controversial, so starting with that sounds good too. And while I kind of agree that the Change process does not seem to be *great* fit for this, but similar changes *have* gone through the Change process before (like https://fedoraproject.org/wiki/Changes/GatingRawhidePackages ). Should a system-wide change (lower case intentional) like this require at least *some* kind of signoff from FESCo? Fabio -- _______________________________________________ devel 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://forge.fedoraproject.org/infra/tickets/issues/new
