https://bodhi.fedoraproject.org/updates/FEDORA-2022-33c88c83fe is pending for 2 days. It appears to be stuck at signing. Newer updates have been pushed to stable since.
There appear to be more such updates at https://bodhi.fedoraproject.org/updates/?releases=F37&page=19 (currently, page 19 is the last, go to the last page if that changes)
Please, push my update to stable and poke the other pending updates as well.
When do you need this? soon
When is this no longer needed or useful? when a new update is made
If we cannot complete your request, what is the impact? updates with fixes never delivered
https://bodhi.fedoraproject.org/updates/FEDORA-2022-531c695a5e https://bodhi.fedoraproject.org/updates/FEDORA-2022-a0b9bb6e41 https://bodhi.fedoraproject.org/updates/FEDORA-2022-33c88c83fe https://bodhi.fedoraproject.org/updates/FEDORA-2022-7fbe013a59 https://bodhi.fedoraproject.org/updates/FEDORA-2022-48eacc985a https://bodhi.fedoraproject.org/updates/FEDORA-2022-213fef8ec7
All the updates are for Fedora 37 but have fc36 dist tag. They are tagged into:
f36-updates-testing-pending f37-signing-pending f37-updates-candidate
Seems like a mid-branching problem.
These seem to have been built right when mass branching was happening and signing wasn't in place yet.
I've re-tagged all of them into f37-signing-pending so robosignatory can see the message and process them.
Hopefully thats all thats needed.
Probably also tagging them to f36?
The updates went stable but are still tagged to f36-updates-testing-pending. I suppose Bodhi won't allow another update from the same build, so tagging them manually to f36 seems like the best option to me.
Yeah, I guess thats least bad. Will do that.
done.
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Thank you.