It looks like there was a
pipewire update late last night on Fedora 38, however when I try to update via
dnf update I get a warning saying that the
pipewire package update will be skipped.
[scott@fedora ~]$ yay
[sudo] password for scott:
Copr repo for PyCharm owned by phracek 16 kB/s | 2.1 kB 00:00
Fedora 38 - x86_64 84 kB/s | 25 kB 00:00
Fedora 38 openh264 (From Cisco) - x86_64 3.1 kB/s | 989 B 00:00
Fedora Modular 38 - x86_64 58 kB/s | 24 kB 00:00
Fedora 38 - x86_64 - Updates 44 kB/s | 19 kB 00:00
Fedora Modular 38 - x86_64 - Updates 57 kB/s | 23 kB 00:00
google-chrome 6.4 kB/s | 1.3 kB 00:00
RPM Fusion for Fedora 38 - Free 3.4 kB/s | 3.4 kB 00:01
RPM Fusion for Fedora 38 - Free - Updates 32 kB/s | 3.8 kB 00:00
RPM Fusion for Fedora 38 - Nonfree 52 kB/s | 6.7 kB 00:00
RPM Fusion for Fedora 38 - Nonfree - NVIDIA Driver 43 kB/s | 6.9 kB 00:00
RPM Fusion for Fedora 38 - Nonfree - Steam 12 kB/s | 6.1 kB 00:00
RPM Fusion for Fedora 38 - Nonfree - Updates 13 kB/s | 6.7 kB 00:00
vivaldi 18 kB/s | 3.0 kB 00:00
Problem 1: package pipewire-codec-aptx-0.3.74-1.fc38.x86_64 from @System requires pipewire = 0.3.74, but none of the providers can be installed
- cannot install both pipewire-0.3.75-1.fc38.x86_64 from updates and pipewire-0.3.74-1.fc38.x86_64 from @System
- cannot install the best update candidate for package pipewire-codec-aptx-0.3.74-1.fc38.x86_64
- cannot install the best update candidate for package pipewire-0.3.74-1.fc38.x86_64
Problem 2: problem with installed package pipewire-codec-aptx-0.3.74-1.fc38.x86_64
- package pipewire-codec-aptx-0.3.74-1.fc38.x86_64 from @System requires pipewire = 0.3.74, but none of the providers can be installed
- package pipewire-codec-aptx-0.3.74-1.fc38.x86_64 from rpmfusion-free-updates requires pipewire = 0.3.74, but none of the providers can be installed
- package pipewire-0.3.74-1.fc38.x86_64 from @System requires pipewire-libs(x86-64) = 0.3.74-1.fc38, but none of the providers can be installed
- cannot install both pipewire-libs-0.3.75-1.fc38.x86_64 from updates and pipewire-libs-0.3.74-1.fc38.x86_64 from @System
- cannot install the best update candidate for package pipewire-libs-0.3.74-1.fc38.x86_64
Package Arch Version Repo Size
bind-libs x86_64 32:9.18.17-1.fc38 updates 1.3 M
bind-license noarch 32:9.18.17-1.fc38 updates 15 k
bind-utils x86_64 32:9.18.17-1.fc38 updates 223 k
curl x86_64 8.0.1-3.fc38 updates 349 k
glib2 x86_64 2.76.4-3.fc38 updates 2.8 M
libcurl-minimal x86_64 8.0.1-3.fc38 updates 250 k
libopenmpt x86_64 0.6.11-1.fc38 updates 637 k
libsmbclient x86_64 2:4.18.5-0.fc38 updates 82 k
libtracker-sparql x86_64 3.5.3-2.fc38 updates 385 k
libwbclient x86_64 2:4.18.5-0.fc38 updates 48 k
osinfo-db noarch 20230719-1.fc38 updates 433 k
pipewire-jack-audio-connection-kit x86_64 0.3.75-1.fc38 updates 17 k
pipewire-jack-audio-connection-kit-libs x86_64 0.3.75-1.fc38 updates 139 k
samba-client x86_64 2:4.18.5-0.fc38 updates 719 k
samba-client-libs x86_64 2:4.18.5-0.fc38 updates 5.3 M
samba-common noarch 2:4.18.5-0.fc38 updates 153 k
samba-common-libs x86_64 2:4.18.5-0.fc38 updates 114 k
tracker x86_64 3.5.3-2.fc38 updates 584 k
vivaldi-stable x86_64 6.1.3035.204-1 vivaldi 94 M
xdg-dbus-proxy x86_64 0.1.4-2.fc38 updates 42 k
Skipping packages with conflicts:
(add '--best --allowerasing' to command line to force their upgrade):
pipewire x86_64 0.3.75-1.fc38 updates 108 k
pipewire-libs x86_64 0.3.75-1.fc38 updates 1.8 M
Upgrade 20 Packages
Skip 2 Packages
Total download size: 108 M
Is this ok [Y/n]:
pipewire-codec-aptx from rpmfusion is using pipewire 0.3.74, Fedora has updated
pipewire to 0.3.75.
They are just out of sync, usually this kind of stuff is resolved in a few days.
You may consider filing an issue with https://bugzilla.rpmfusion.org/ if nobody have not done so already.
Appreciate all the replies and thank you for the answers. Looks like now I know when conflicts like this happen, I’ll need to consider looking into the RPMFusion repos for some of the possible packages it could be. I wasn’t aware
pipewire-codec-aptx was from the RPMFusion repos, but I’ll keep a note of that if there’s a next time.
Will monitor the bug tracker over at Bugzilla until it’s resolved, thanks for the link btw, Mr. @grumpey
Marked as Solved now since the bugzilla report @grumpey linked has now been resolved. Just make sure to do a
sudo dnf upgrade --refresh before you update and you should be good to go. No conflicting packages anymore. Updating now myself. Cheers
Sigh… the issue is back again as an update to pipewire v 0.3.76-1 came out last night, so the conflicts when updating are back. Help us RPMFusion, you’re our only hope.
Edit: I reopened the bug, but I’m not yet familiar with Bugzilla, so I may or may not have done it all right and proper.
I don’t think that this is properly described as a bug. It’s part of how things work when, for various reasons, packages that might be coordinated in the the pure Fedora repo set are not coordinated as tightly between that set and others, such as the RPMFusion set.
If you added some of the audio/video codec-related packages from the latter, you will also experience this regularly for some of the MESA3d packages. More often than not these are cleared up within a few days. The MESA3d developers release upstream updates every three or four weeks.
If you’re using these sorts of package groups, you’ll soon learn which ones are commonly failing to upgrade; you’ll learn to ignore these notices…
If you use the
dnf upgrade command without the
-y you can go thru the list of updates and abort it with
N if you see a update from rpmfusion. Just keep it back for a day or two till it is synchronized.
Especially if the update happens on a weekend I generally wait till the next Monday to do the update.
As now for example:
(I do use already dnf5, it shows the repository it updates from and the version it replaces)
mesa-va-drivers-freeworld x86_64 23.1.4-1.fc38 rpmfusion-free-updates 12.6 MiB
replacing mesa-va-drivers-freeworld x86_64 23.1.3-1.fc38 rpmfusion-free-updates 12.6 MiB
mesa-vdpau-drivers-freeworld x86_64 23.1.4-1.fc38 rpmfusion-free-updates 12.6 MiB
replacing mesa-vdpau-drivers-freeworld x86_64 23.1.3-1.fc38 rpmfusion-free-updates 12.6 MiB
@jrredho @ilikelinux I mean it’s been going on 5 days now with RPMFusion holding back updates. Is something going on with RPMFusion? I’ve tried for days, but I have not been able to communicate with the RPMFusion devs on their official IRC channel since no one ever responds, so I don’t even know what’s going on.
I would be very surprised if the Pipewire devs working on RPMFusion packages weren’t aware of this already. Five days is not a long time. Remember, you’re using a “bleeding edge” distribution. That carries some (temporary, generally) headaches sometimes, and, for certain aspects, some fortitude and some patience.
Here’s a challenge: Go to other distributions and check which versions of Pipewire are current in their respective package repos. My guess is that all of them will be older than what’s distributed in the Fedora/RPMFusion repos, even with the current upgrade delay.
I’ve had the same issue for the last few days so I guess we’ll just have to wait.
It’s possible some maintainers went to Flock or GUADEC recently, so that could be also why the longer delay than usual. Patience it gets taken care of soon though.
Edit: Here’s another relevant link: https://pkgs.rpmfusion.org/cgit/free/pipewire-codec-aptx.git/commit/pipewire-codec-aptx.spec
I can’t speak for the maintainers in question, but apart from the events mentioned Fedora 39 just had its mass rebuild, and before that the Python 3.12 rebuild happened, so… personally I’m spending part the time fixing broken packages and less on upgrading
Just to add after updating today there were no issues so the issue seems resolved.