On Thu, 2026-07-09 at 15:55 +0200, Vít Ondruch wrote: > Dne 06. 07. 26 v 23:16 Fabio Valentini napsal(a): > > 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. > > > +1 including Rawhide / Branched
For Rawhide I have a now-less-Sekrit Plan: https://forge.fedoraproject.org/releng/tooling/src/branch/main/quality-assurance/critpath/ccp.py that's a script that produces a list of "compose-critical packages", i.e. the packages which are used to build, or are included in, the non- failable images in the latest compose. My plan for Rawhide/Branched is to gate updates only if they break the dependencies of any compose- critical package, rather than gating on *all* failures. That still requires a bit work, though. I need to get something to expose the compose-critical package data in a convenient way, and it's probably Bodhi, since it's Bodhi that stores and exposes the critical path package list (and I want Bodhi to use compose-critical package info for other reasons too). Then I have to adjust rmdepcheck and/or the CI pipeline to somehow make it convenient to distinguish between a 'ccp' and 'non-ccp' failure... I suppose we *could* decide it's fine to gate Rawhide on all rmdepcheck failures and just require people to waive cases where they intentionally break other deps? Meh. I dunno. -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @[email protected] https://www.happyassassin.net -- _______________________________________________ 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
