Some updates I submitted yesterday (which I wanted to finish before the outage started, but alas, koji broke earlier than that, so the builds finished during only at some point during the outage ) are now stuck in bodhi because the builds are not getting signed:
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-96efab0b6c
When do you need this? (YYYY/MM/DD)
It would be great if this could get fixed within the next few days, but before the mass branching (2024-02-13) at the latest to avoid additional work due to updates getting unpushed / borked.
N/A
A dozen updates remain stuck and / or are possibly getting unpushed during mass branching, making it necessary for me to bump-release-and-rebuild 15 packages in 4 branches each.
Metadata Update from @kevin: - Issue assigned to kevin
Yeah, koji was working and tagging things, but not emitting messages, so autosign didn't know to do anything. ;(
I am cleaning all these up now by retagging them (from the bodhi user, since autosign actually refuses if it's not the bodhi user who tagged it)
FWIW I've also seen my updates submitted yesterday and those from other users which were in fact signed and with a request pending -> testing were not pushed in the last compose. In the message history I see several test gating status change which were probably the cause of those updates not being pushed in the compose. For example: https://bodhi.fedoraproject.org/updates/FEDORA-2024-b54c948041 https://bodhi.fedoraproject.org/updates/FEDORA-2024-84d0cc59e1
Let's see if the next compose goes better. @adamwill maybe you have some idea about what happened?
ok. All of them (and others) should be fixed.
Please re-open/let me know if you see any missed ones.
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
There was no updates pushes last night. I disabled them due to koji being down.
So, I think it should all go in the next compose...