Learn more about these different git repos.
Other Git URLs
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-b1ed1bcdeb When this update got processed the package got put in testing and I can build against it, but the update is stuck in a pending state. Looks like some tagging config is missing.
Looks like there's a bunch of updates that got the same result: https://bodhi.fedoraproject.org/updates/?releases=EPEL-9&page=1
I seem to have the same issue with https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-2454913940
I pushed it agin and it came with back with the same status after a day or so.
I think something really wrong happened during the compose two days ago. All these packages (see also https://pagure.io/fedora-infrastructure/issue/10493 ) were tagged into epel9-testing and removed from epel9-testing-candidate, but the Bodhi updates were not marked as "in testing".
epel9-testing
epel9-testing-candidate
Pushing them again in Bodhi was not enough, since builds were missing the epel9-testing-candidate, which is expected when the update goes from "pending" to "testing".
I have now manually untagged all those builds from epel9-testing and manually tagged them in epel9-testing-candidate and pushed the updates.
However, Bodhi has once again started to show a lot of 500 errors. I'm not sure if that's the cause or the problem was on Koji side (https://pagure.io/releng/issue/10564 happened at the same time and had nothing to do with Bodhi). (see discussion about 500 Errors on https://github.com/fedora-infra/bodhi/issues/4344)
I've the same issue with:
How to get them to EPEL testing now?
Seems like @humaton fixed them, but waiting for the next push to verify it.
Metadata Update from @mohanboddu: - Issue tagged with: medium-gain, medium-trouble, ops
Updates are pushed.
Metadata Update from @humaton: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.