Comments

133 Comments

I have a neovim conflict on my system:

Problem: package neovim-0.10.1-1.fc40.x86_64 from @System requires libtree-sitter.so.0()(64bit), but none of the providers can be installed - cannot install both libtree-sitter-0.23.0-1.fc40.x86_64 from imladris_f40_x86_64_f40_x86_64_updates_testing and libtree-sitter-0.22.5-1.fc40.x86_64 from @System - cannot install both libtree-sitter-0.23.0-1.fc40.x86_64 from imladris_f40_x86_64_f40_x86_64_updates_testing and libtree-sitter-0.22.2-1.fc40.x86_64 from imladris_f40_x86_64_release - cannot install both libtree-sitter-0.23.0-1.fc40.x86_64 from imladris_f40_x86_64_f40_x86_64_updates_testing and libtree-sitter-0.22.5-1.fc40.x86_64 from imladris_f40_x86_64_f40_x86_64_updates - cannot install the best update candidate for package neovim-0.10.1-1.fc40.x86_64 - cannot install the best update candidate for package libtree-sitter-0.22.5-1.fc40.x86_64 ==================================================================================================== Package Arch Version Repository Size ==================================================================================================== Skipping packages with conflicts: (add '--best --allowerasing' to command line to force their upgrade): libtree-sitter x86_64 0.22.2-1.fc40 imladris_f40_x86_64_release 101 k libtree-sitter x86_64 0.23.0-1.fc40 imladris_f40_x86_64_f40_x86_64_updates_testing 102 k

Transaction Summary

Skip 2 Packages

Nothing to do. Complete!

karma

Downloaded and tested from koji. LGTM!

BZ#2272953 Release 45.1 "officially" supports GNOME 46
karma

The bluetooth regression (BZ#2274047) is definitely fixed in this. No other regressions noted.

BZ#2274047 Bluetooth headset partially connects under some circumstances with blues 5.73-3.fc40.x86_64
karma

Tested from Koji, rendered Chrome and VScode correctly as hoped

karma

I have seen the brokenness with both Chrome and VSCode.

Should this update be unpushed?

karma

Tested with freeipa-provided subid's successfully. LGTM

karma

LGTM; confirm that this fixes the issue with installing signed collections

BZ#2171961 toolbox-0.0.99.4 is available
karma

LGTM! Also tested specifically with FreeIPA provided subid's. When not configured correctly, toolbox still fails as expected.

BZ#2171961 toolbox-0.0.99.4 is available

Seems the current spec still has a %package quadlet:

%package quadlet
Summary: Easily create systemd services using %{name}
Requires: %{name} = %{epoch}:%{version}-%{release}
Conflicts: quadlet

I don't know if that explains the behavior, but I think the conflicts belongs in the main package now, at least

I definitely had to remove podman-quadlet manually. I'm looking at the specfile and I see the obsoletes line, and it appears to be correct.

Updating Subscription Management repositories. Transaction ID : 695 Begin time : Thu 09 Feb 2023 08:38:05 AM CST Begin rpmdb : 1e4cd75cbd9ba87adccd9919af8123226f00136441e8e4a2d4cf099eb7ca35b1 End time : Thu 09 Feb 2023 08:38:06 AM CST (1 seconds) End rpmdb : db15e28b7e950e8269ca18d663af7c8c5469298e649d82ee1773ab95bef9c0da User : Martin Jackson <mjackson> Return-Code : Success Releasever : 37 Command Line : erase podman-quadlet Comment : Packages Altered: Removed podman-quadlet-5:4.4.0-1.fc37.x86_64 @@System

(From the manual removal) vs:

Obsoletes: %{name}-quadlet <= 5:4.4.0-1

in the current specfile. So I'm not sure why I would have had to do that...

karma

Pulled from the koji builds. Works for rootless and rootful containers.

Note that the previously built subpackage podman-quadlet has now been integrated into the podman binary package in this release. You will need to remove podman-quadlet manually if you have one.

I think that depends on https://bodhi.fedoraproject.org/updates/FEDORA-2023-041092cd8f which should hit stable before podman does