Describe the issue For some reason, libavif-1.0.4-7.el10_0 didn't get an epel10.0 tag. It went through bodhi, and bodhi said it was getting pushed to stable. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-6d4f4b0568 But in the end, it was left with no tag. This is the history: Fri Sep 20 07:28:00 2024 libavif-1.0.4-7.el10_0 tagged into epel10.0-testing-candidate by tdawson Fri Sep 20 07:28:54 2024 libavif-1.0.4-7.el10_0 tagged into epel10.0-signing-pending by bodhi Fri Sep 20 07:29:53 2024 libavif-1.0.4-7.el10_0 untagged from epel10.0-signing-pending by autosign/autosign02.iad2.fedoraproject.org Fri Sep 20 07:29:53 2024 libavif-1.0.4-7.el10_0 tagged into epel10.0-testing-pending by autosign/autosign02.iad2.fedoraproject.org Fri Sep 20 07:32:23 2024 libavif-1.0.4-7.el10_0 untagged from epel10.0-testing-pending by bodhi Fri Sep 20 07:32:23 2024 libavif-1.0.4-7.el10_0 untagged from epel10.0-testing-candidate by bodhi
When do you need this? (YYYY/MM/DD) 2024/09/24
When is this no longer needed or useful? (YYYY/MM/DD) When a newer build get's built and properly tagged in.
If we cannot complete your request, what is the impact? For some reason I can't even create an override. Several packages require libavif to build in epel10. They also need it for runtime stuff. Those various packages, and their dependencies, will not be able to build, or run in epel10.
This was due to problems with buildvm-ppc64le-20.
https://koji.fedoraproject.org/koji/taskinfo?taskID=123701154
the tag failed. ;(
I suppose we should go look at all the failures and fix them.
ok, I resubmitted all the failed tag tasks from bodhi.
I think this should be all back to normal now, please re-open if there's anything futther to do.
I suppose we could file a RFE for bodhi upstream to note errors like these when they happen?
Metadata Update from @kevin: - Issue close_status updated to: Fixed with Explanation - Issue status updated to: Closed (was: Open)