Backport upstream fixes to fix keyboard layout sorting in the initial setup session.
sudo dnf upgrade --refresh --advisory=FEDORA-2022-b14944cb83
Please login to add feedback.
|0||0||Test Case Gnome Accessibility|
|0||0||Test Case Gnome Classic mode|
|0||0||Test Case Gnome Lock Screen|
|0||0||Test Case Gnome Login Screen|
|0||0||Test Case gnome desktop background|
|0||0||Test Case gnome-shell activities|
|0||0||Test Case gnome-shell dash|
|0||0||Test Case gnome-shell extensions gnome org|
|0||0||Test Case gnome-shell extensions install|
|0||0||Test Case gnome-shell extensions remove|
|0||0||Test Case gnome-shell overview search|
|0||0||Test Case gnome-shell workspaces|
This update has been submitted for testing by kalev.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'failed'.
This seems to depend on mutter-43.0-2.fc37 , which is only in updates-testing, so these two updates should be grouped together, otherwise dependencies will get broken if this is pushed first.
Hm, there's something else going on with the tests. These two shouldn't depend on each other at all.
What I think is going on is that https://bodhi.fedoraproject.org/updates/FEDORA-2022-0bd68bbb43 was pushed to stable last night, but the F37 compose that includes the new packages is still running and openqa hasn't picked up the new mutter that was in that update yet because of that.
Yes, I think you're right.
This update has been pushed to testing.
This update's test gating status has been changed to 'passed'.
"What I think is going on is that FEDORA-2022-0bd68bbb43 was pushed to stable last night, but the F37 compose that includes the new packages is still running and openqa hasn't picked up the new mutter that was in that update yet because of that."
Yes, that was the situation. I did add comments to the failed tests explaining this. For Branched and Rawhide, updates that are "pushed stable" still only really become available after the next successful nightly compose, because we do not use an updates repo for development branches; what actually happens when an update is "pushed stable" is simply that it is tagged
f38or whatever. It doesn't go anywhere until the next nightly compose happens, into which it is now pulled because it's tagged, and if that compose succeeds, it gets synced to the live repos.
Works for me. No regressions noted compared to previous version.
This update has been submitted for stable by bodhi.
This update has been pushed to stable.