Learn more about these different git repos.
Other Git URLs
There's a handful of f39 updates that are stuck in the "testing → stable" state because they keep getting ejected from the f39-updates compose. I'm not sure what's the cause here, but it might be related to the recent network / AMQP outage (all updates had their initial → stable push request on Sep. 06):
sile-0.14.17-1.fc39: https://bodhi.fedoraproject.org/updates/FEDORA-2024-2f7519eae3
When do you need this? (YYYY/MM/DD)
Before F39 EOL.
After F39 EOL.
9 updates are lost in limbo.
Metadata Update from @jnsamyak: - Issue tagged with: low-gain, low-trouble, ops
Metadata Update from @jnsamyak: - Issue assigned to jnsamyak
I did a request a stable push request for bodhi, hopefully it will fix this issue: https://bodhi.fedoraproject.org/composes/F39/stable
Yikes, so I checked, and it seems like that these builds are not tagged properly!
For example:
FEDORA-2024-d867e27150 ejected from the push because "Cannot find relevant tag for python-wikitcms-2.6.13-1.fc39. None of ['f39-updates', 'f39-updates-candidate', 'f39-updates-pending'] are in ['epel9-next-testing', 'eln-updates-testing', 'epel8-testing', 'epel9-testing', 'f40-container-updates-testing', 'f39-updates-testing', 'f39-container-updates-testing', 'f39-flatpak-updates-testing', 'f41-container-updates-testing', 'f41-updates-testing', 'f42-updates-testing', 'f40-flatpak-updates-testing', 'f40-updates-testing', 'f42-container-updates-testing', 'f42-flatpak-updates-testing', 'f41-flatpak-updates-testing', 'epel10.0-testing']."
I can manually tag these builds to f39-updates-candidate and it should go stable in the next compose tonight
Looking at the history, these builds were already tagged by @kevin Not sure what is wrong here:
One such example:
Sun Sep 8 21:01:44 2024 nfs-utils-2.7.1-0.fc39 tagged into f39-updates-candidate by kevin [still active] Mon Sep 9 05:44:05 2024 nfs-utils-2.7.1-0.fc39 untagged from f39-updates-pending by bodhi
Should we consider retagging them?
Found some f41 updates that seem to be affected too:
https://bodhi.fedoraproject.org/updates/FEDORA-2024-e5d9fcb26c https://bodhi.fedoraproject.org/updates/FEDORA-2024-da5e1e1ae0
The httpd update is a security update, so it would be great if that one landed before GA.
The problem here is that bodhi expects them to be in f39-updates-testing (they are all going stable), but they aren't. (as it says in the message :)
I have tagged them all into f39-updates-testing, so they should go out today I hope. Lets see.
Ditto the 2 f41 ones, I also tagged them into f41-updates-testing.
Looks good to me now, thank you!
Metadata Update from @decathorpe: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.