Can't update pipewire-codec-aptx: "nothing provides pipewire >= 0.3.69"

Ask Fedora
, , ,
1

I run into this problem when trying to update:

[root@rife ~]# dnf update --best --allowerasing
Last metadata expiration check: 0:07:19 ago on Fri 21 Apr 2023 23:34:59 BST.
Error: 
 Problem: cannot install the best update candidate for package pipewire-codec-aptx-0.3.67-1.fc36.x86_64
  - problem with installed package pipewire-codec-aptx-0.3.67-1.fc36.x86_64
  - nothing provides pipewire >= 0.3.69 needed by pipewire-codec-aptx-0.3.69-1.fc36.x86_64
(try to add '--skip-broken' to skip uninstallable packages)

I saw the same thing when last weekend.

If this is what it looks like, how come there is a version of pipewire-codec-aptx which requires a version of pipewire which isn’t available?

pipewire-codec-aptx is from rpmfusion-free-updates, whereas pipewire is from @System. I am still on F36 . Has RPMFusion somehow got out of sync with Fedora here?

I don’t even know what pipewire-codec-aptx or why it’s installed. Apparently no other package depends on it.

1 Like
2

AptX is a Qualcom proprietary audio codec compression algorithm. The codec is needed to use “aptX enabled” bluetooth audio devices so it makes sense that no other packages require it.

3

pipewire-codec-aptx is part of the Multimedia package group if you have rpmfusion-free repo enabled.

You most likely followed these steps to update the Multimedia group.

You can check the transaction history for a package:

dnf history list pipewire-codec-aptx
dnf history info <transaction-id>

Seems like pipewire 0.3.69-1 didn’t make it to F36 because it didn’t get enough feedback from testers before 0.3.69-2, then the same thing happened to 0.3.69-2 before 0.3.70-1.

The easiest course of action is to simply exclude pipewire-codec-aptx from updates while waiting for pipewire 0.3.70-1.

dnf upgrade -x pipewire-codec-aptx

If you want 0.3.70-1 to reach F36 sooner, you can help to test it by following the install instructions on the page. See here for more information on testing and leaving feedback on Bodhi.

Updates going slightly out of sync between Fedora and RPM Fusion is fairly common and harmless, usually resolved by waiting a day or two. This one might take longer depending on when enough people test and provide feedback.

4

Note that testing requires hardware that supports aptX.