Comments

263 Comments

This update has been unpushed.

Thanks for testing. I don't know how I missed that. Unpushing the update and working on a fix.

This update has been unpushed.

karma

mock --no-bootstrap-chroot --arch=armv7hl -r fedora-36-armhfp fails for me with:

ERROR: 'armv7hl'
Traceback (most recent call last):
  File "/usr/libexec/mock/mock", line 1065, in <module>
    exitStatus = main()
  File "/usr/lib/python3.10/site-packages/mockbuild/trace_decorator.py", line 93, in trace
    result = func(*args, **kw)
  File "/usr/libexec/mock/mock", line 687, in main
    check_arch_combination(config_opts['rpmbuild_arch'], config_opts)
  File "/usr/lib/python3.10/site-packages/mockbuild/trace_decorator.py", line 93, in trace
    result = func(*args, **kw)
  File "/usr/libexec/mock/mock", line 532, in check_arch_combination
    binary = f'/usr/bin/qemu-{config_opts["qemu_user_static_mapping"][config_opts["forcearch"]]}-static'
KeyError: 'armv7hl'

@imabug -2 build no longer requires typing-extensions, please retest.

@g6avk Yes, I backported upstream patch that removed the dependency. Thanks for testing.

Thank you for reverting the initscript change. This was the right thing to do.

karma

I've just stumbled upon the IPv6 translation issue and found this update.

Apart from fixing the IPv6 translation, this update brings a new initscript with changed behaviour (no autosave on shutdown by default) and new location for saved ipsets. This kind of change should not happen in the middle of stable branch lifecycle. See https://bugzilla.redhat.com/show_bug.cgi?id=2052926 and https://src.fedoraproject.org/rpms/ipset/c/2c76e0d4d85066a8ab98a0cd506e88f172c702df?branch=f36 for more details.

This is an example why merging down from rawhide to older branches is sometimes a bad idea.

Please unpush this build and submit a build with only upstream fixes applied, without the initscript change (https://src.fedoraproject.org/rpms/ipset/tree/2c76e0d4d85066a8ab98a0cd506e88f172c702df).

karma

Fixes display issues and kernel panic on my 11th Gen Intel laptop that occur with 5.9.12. All good now.

Same here on Intel(R) Iris(R) Xe Graphics [0x9a49].

karma

UI is half-broken for me. Everything is too big on a 13" 1920x1080 laptop screen.

Test Case firefox addons
Test Case firefox browse
karma

Confirmed, h264 videos play again.

BZ#2089986 ffmpeg: [libopenh264 @ 0x7f72200022c0] Incorrect library version loaded
karma

Works for me here and no more errors about .so files not being found.

BZ#2079740 hplip-3.22.4 is available
BZ#2080235 Misleading errors about missing shared libraries when scanning

I wonder why nobody noticed the issue I've just reported in #2082857 .

Thanks for testing! You can revert to the previous one in preferences.

User Icon rathann commented & provided feedback on wine-7.5-1.fc36 a year ago

Hold on. I can understand depending on MinGW libraries, but why is the update pulling in development stuff like:

isl
mingw-binutils-generic
mingw32-binutils
mingw32-cpp
mingw32-gcc
mingw32-headers
mingw64-binutils
mingw64-cpp
mingw64-gcc
mingw64-headers

The above should not be needed to run wine.

User Icon rathann commented & provided feedback on wine-7.5-1.fc35 a year ago

Hold on. I can understand depending on MinGW libraries, but why is the update pulling in stuff like:

isl
mingw-binutils-generic
mingw32-binutils
mingw32-cpp
mingw32-gcc
mingw32-headers
mingw64-binutils
mingw64-cpp
mingw64-gcc
mingw64-headers

The above should not be needed to run wine.

I can live with Recommends: earlyoom instead of Requires:. I'd change my vote here in that case. I'm not sure why you thought you needed to create a new subpackage just for fixing #2068699. You could have added the Conflicts: systemd-oomd-defaults and Recommends: earlyoom to the -configs subpackage. Each new subpackage increases the amount of repo metadata that dnf has to process. Please revert creation of the -systemd subpackage and fold it back into -configs.

You are missing my point. I can uninstall systemd-oomd-defaults, but I can't uninstall earlyoom after installing this update. It makes things worse for me, hence the negative karma.

FWIW, nothing requires systemd-oomd-defaults, not even weakly, so it can be uninstalled with no dependency issues.