Re: Proposal: gate all stable release updates on rmdepcheck

Adam Williamson <[email protected]>
Newsgroups gmane.linux.redhat.fedora.devel
Message-ID <[email protected]>
On Thu, 2026-07-09 at 10:41 -0700, Kevin Fenzi wrote:
> On Thu, Jul 09, 2026 at 04:27:19PM +0100, Adam Williamson wrote:
> > 
> > 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.
> 
> Conceptually, that sounds fine to me... if you know you are breaking
> deps for some reason (thing not ready, but very leaf node, etc) doing a
> waiver to note that would make sense too.
> 
> However, it does mean you (and anyone who watches waivers) will probibly
> see more that you need to look at and see if they look reasonable.

I don't really actively monitor waivers currently. It's more like, I
look at broken stuff, and look for a waiver if it seems like it would
involve one.

So if we did this...I suspect if we saw a compose fail because of
broken dependencies, or some significant package broke and people
started complaining, I'd go look for a waiver.

> Is there any easy way to be notified on all waivers? 

Well, FMN, I guess. There's a message published for each waiver. Other
than that, not that I know of.
-- 
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
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.