On Fri, Jul 10, 2026 at 08:13:53PM +0100, Adam Williamson wrote: > > 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).
yes. But even the manual ones emit a message... foo requested update bar to stable. > > 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. Yep. I think it shouldn't be too hard to hook into the second one, but of course that hits the issue you mentioned... checking against anything thats requested stable at the same time could result in some failure that you have to just not push anything or have a complex way to solve. And there's no concept of a waiver for that either. So, yeah, I would say leaving that for the future(tm) would be best. kevin -- _______________________________________________ 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
