I'd followed https://docs.fedoraproject.org/en-US/rawhide-gating/multi-builds/ to submit an update last evening https://bodhi.fedoraproject.org/updates/FEDORA-2020-641e69f08c
and 8 hours later, it appears to be stuck in a 'pending' state. I'd asked on #fedora-devel this morning about it, and pingou thought there was something wrong and that I should submit this issue.
Looking at the tag via koji buildinfo analitza-19.12.3-2.fc33 it looks like the builds have not been moved to a -pending-signing tag which the bodhi UI confirms (the builds aren't signed).
koji buildinfo analitza-19.12.3-2.fc33
Something missed a notification?
I see four more updates that are stuck in pending across various releases:
From what I can tell, they're not getting moved into the right koji tags, and the builds are not signed yet (though the python builds are stuck in f32-pending-signing for two days).
Metadata Update from @cverna: - Issue assigned to cverna
Metadata Update from @cverna: - Issue priority set to: Waiting on Assignee (was: Needs Review)
Any ETA to get this resolved, this is blocking other work I'd like to get done.
So the update is currently blocked because of
This update cannot be pushed to stable. These builds qt-creator-4.12.0-0.2.beta1.fc33 have a more recent build in koji's f33 tag.
If you think that these builds are not needed in the side tag any more you should remove them from the tag using
koji untag f3x-build-side-nnnnn offending-nvr
then Edit the update in Bodhi and click the update/refresh button in the builds table, in order to refresh the list of builds in the update. That should unblock the update.
I was worried that stuff like that may happen... the more this gets delayed... the more chances that newer builds will show up. :( I'll remove qt-creator and we'll see.
Seems that qt5-qtbase-5.14.2-1.fc33 is now conflicting.
arg, I'll try ejecting that one and see. herding cats is hard
Made it to stable :-)
thanks for your help
@decathorpe I believe that your updates will be pushed to testing now that the builds have the correct candidate tag. I am closing that ticket but please reopen if anything goes wrong.
Metadata Update from @cverna: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
@cverna yeah I think my three updates should be OK now. I tagged the builds with f3x-updates-candidate manually, and now the updates seem to be un-stuck.
Login to comment on this ticket.