Learn more about these different git repos.
Other Git URLs
Describe the issue Between FEDORA-2022-1cf62664a8 (waybar-0.9.10-1.fc36) and FEDORA-2022-592fded23f (waybar-0.9.12-1.fc36), the earlier build somehow got composed into the f36 stable repo and the latter one remains in f36 updates-testing. Both builds were in pending->stable at the moment of the compose run, both are now marked as stable. I believe at this point releng help is needed to tag the right build into f36. From a brief look, none of my other updates are in the same state.
pending->stable
stable
When do you need this? (YYYY/MM/DD) Preferably before the final freeze.
When is this no longer needed or useful? (YYYY/MM/DD)
If we cannot complete your request, what is the impact? 0.9.10 has a couple of high impact bugs, making this release nigh unusable.
there was an issue with a couple of bodhi updates. I can see waybar 0.9.12 in my f36 install.
Metadata Update from @humaton: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
dnf distro-sync waybar --disablerepo updates-testing --refresh ... Downgrading: waybar x86_64 0.9.10-1.fc36 fedora 452 k dnf distro-sync waybar --disablerepo * --enablerepo koji-f36 --refresh ... Downgrading: waybar x86_64 0.9.10-1.fc36 koji-f36 452 k
(koji-f36 is https://kojipkgs.fedoraproject.org/repos/f36-build/latest/$basearch/)
https://kojipkgs.fedoraproject.org/repos/f36-build/latest/$basearch/
0.9.12 comes from updates-testing, but it's not even supposed to be there. And since the corresponding update is already marked as stable, I don't expect that bodhi will try to move the build to the stable repo again.
Login to comment on this ticket.