On Wed, Mar 19, 2025 at 10:26:33AM +0100, Dmitry Belyavskiy wrote: > Dear Petr, > Thank you for the investigation! > I think it happened because the build happened during the freeze. It happened right at the time updates-testing was enabled for f42/branched. So, when the build/update was automatically created it was acting like a rawhide update. But it failed gating, then when it passed a few hours later it was in the wrong 'flow' to go to updates-testing. If maintainers see this issue, probibly the easiest/quickest fix is to just tag the build into the fN-updates-candidate tag (ie, f42-updates-candidate), which any maintainer can do with a 'koji tag-build f42-updates-candidate NVR). kevin -- _______________________________________________ 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
