On Fri, 2026-07-10 at 12:07 -0700, Kevin Fenzi wrote: > On Fri, Jul 10, 2026 at 07:11:38PM +0100, Adam Williamson wrote: > > On Fri, 2026-07-10 at 18:21 +0100, Michel Lind wrote: > > > One tweak to this - can we force a re-run before promoting a package > > > from testing->stable as well, because as the example above showed (this > > > is the rpki 0.19.3-1 update vs the quick-xml 0.41 update, FWIW) - > > > testing once might not be enough as the state might have changed in > > > subsequent composes? > > > > It's not trivial to do that, unfortunately, no. I don't think we need > > to solve that to implement the initial gating, though. > > > > The way we actually do "promotion" for stable releases is that, once a > > day (usually, IIRC), a Bodhi task running on a timer tags all updates > > queued for stable at the time, assuming some other last-minute sanity > > checks pass. (Then there's a compose which causes the tagged packages > > to actually get sent out; I don't recall if that's part of the same > > process, or a separate one). > > My memory could be faulty, but I don't think thats how it's setup. > There's a celery task that runs every ~5min and checks all the updates > to see if they met stable requirements, if they have it adds the request > to stable for them.
Right, but that's just the *request* for stable, right? Not the actual *push*. (And the thing you're describing is the *automatic* request mechanism, that requests stable when the update meets one of the autopush thresholds - manual requests are also possible). > Then, once a day there's composes that actually process those requests. Sure, I guess that's the bit I was remembering/describing. So really there's sort of three points: 1. Update submitted / edited 2. Request for stable happens 3. Stable push happens right? Right now we are only running rmdepcheck (and all other tests outside of Bodhi's internal sanity checks) at 1. -- 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
