Comments

566 Comments

Awesome, thanks for testing!

Works fine in quick testing (and the new build makes it work in a wayland session as well)

Note that this is a continuation of FEDORA-2022-5b019245ff that got unpushed because of broken dependencies. This update here now adds a libavif0.10 compat package to avoid this issue (the compat package is for third party packages; everything in Fedora is rebuilt), and hopefully gets the update over the finish line.

I did a libavif0.10 compat package to help get this one over the finish line and submitted it all again as FEDORA-2022-c8eab6e6f1

I went ahead and did a libavif0.10 compat package to fix the issue with the soname/ABI changing and breaking other packages.

ngompa also suggested that we enable rav1e support for EPEL 9, so I went ahead and did that too while at this.

karma

Haven't noticed any regressions.

Haven't noticed any issues here.

karma

-1 as it needs rebuilds of dependencies (gnome-builder, gnome-console) for the ABI changes.

I couldn't spot any regressions in quick testing. I don't have Enterprise wifi here but kparal already covered that part.

Can you also rebuild dependent packages that use the gtk4 ABI?

karma

Haven't noticed any regressions here.

@burakdede Maybe you can mention it upstream at https://gitlab.gnome.org/GNOME/gdk-pixbuf ? This fix here (backport of https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/merge_requests/143) definitely helps, but is apparently not enough to fix all cases.

I missed one rebuild, should have had mutter-43.0-3.fc38 here as well.

Untagging as a number of openQA tests appear to have started failing with this build.

Untagging as a number of openQA tests appear to have started failing with this build.

Unpushing as a number of openQA tests appear to have started failing with this build.

Note that this depends on latest selinux-policy, FEDORA-2022-839f7bd62c (queued for stable) so we are going to get openqa test failures until new selinux-policy appears in a compose.

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 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.