On Tue, Mar 11, 2025 at 8:32 PM Michael Catanzaro <mcatanzaro@xxxxxxxxxx> wrote: > > I'm pretty concerned that we have no automation to catch these > problems. Would we have even noticed if not for you manually checking > and complaining here on devel@? Probably not. Which is why I do this kind of thing twice a year :) Putting some automation into place would be great. It wouldn't even need to be something that happens on an ongoing basis ... But I don't know if it wouldn't be too frustrating for packagers because of false positives: I do filter out manually a nontrivial amount of "downgrades" that are caused by stuff like "the updates-testing compose for Fedora stable finished two hours earlier than the updates-testing compose for Fedora branched, and I hit the mirrors at a bad time of day so got the updates from one but not the other" ... etc. - so I manually check bodhi if the "missing" update is actually there. I also don't include packages that are FTBFS in the list, since those obviously can't be updated in Branched / Rawhide. Fabio -- _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx 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/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
