Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#77587 - [pipewire] /usr/bin/pipewire-avb exists in both 'pipewire' and 'pipewire-audio'

Attached to Project: Arch Linux
Opened by Frederic Bezies (fredbezies) - Monday, 20 February 2023, 19:10 GMT
Last edited by Toolybird (Toolybird) - Monday, 20 February 2023, 21:34 GMT
Task Type Bug Report
Category Packages: Testing
Status Assigned
Assigned To Jan Alexander Steffens (heftig)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 5
Private No

Details

Description: I tried to update to pipewire 0.3.66-2 and I'm unable to do so.

Here is the error log:

error: failed to commit transaction (conflicting files)
/usr/bin/pipewire-avb exists in both 'pipewire' and 'pipewire-audio'
/usr/lib/pipewire-0.3/libpipewire-module-avb.so exists in both 'pipewire' and 'pipewire-audio'
/usr/lib/pipewire-0.3/libpipewire-module-rtp-sink.so exists in both 'pipewire' and 'pipewire-audio'
/usr/lib/pipewire-0.3/libpipewire-module-rtp-source.so exists in both 'pipewire' and 'pipewire-audio'
/usr/lib/spa-0.2/avb/libspa-avb.so exists in both 'pipewire' and 'pipewire-audio'
/usr/share/pipewire/pipewire-avb.conf exists in both 'pipewire' and 'pipewire-audio'
Errors occurred, no packages were upgraded.


Additional info:
* pipewire-0.3.63-2

Steps to reproduce: just try to update an Archlinux + testing enabled installation.

You'll get stop because of /usr/bin/pipewire-avb
This task depends upon

Comment by Toolybird (Toolybird) - Monday, 20 February 2023, 19:43 GMT
Cannot repro. I just enabled [testing] in an already configured Gnome VM and the upgrade went through fine.
Comment by Frederic Bezies (fredbezies) - Monday, 20 February 2023, 19:55 GMT
Cannot reproduce it too. Looks like it was a bad time update... I have been too quick opening this bug report. Ouch :(
Comment by Alex (BS86) - Monday, 20 February 2023, 19:58 GMT
have it, too:
error: failed to commit transaction (conflicting files)
/usr/include/pipewire-0.3/pipewire/array.h exists in both 'pipewire' and 'libpipewire'
/usr/include/pipewire-0.3/pipewire/buffers.h exists in both 'pipewire' and 'libpipewire'
/usr/include/pipewire-0.3/pipewire/client.h exists in both 'pipewire' and 'libpipewire'
/usr/include/pipewire-0.3/pipewire/conf.h exists in both 'pipewire' and 'libpipewire'
/usr/include/pipewire-0.3/pipewire/context.h exists in both 'pipewire' and 'libpipewire'
/usr/include/pipewire-0.3/pipewire/control.h exists in both 'pipewire' and 'libpipewire'
/usr/include/pipewire-0.3/pipewire/core.h exists in both 'pipewire' and 'libpipewire'
/usr/include/pipewire-0.3/pipewire/data-loop.h exists in both 'pipewire' and 'libpipewire'
/usr/include/pipewire-0.3/pipewire/device.h exists in both 'pipewire' and 'libpipewire'
/usr/include/pipewire-0.3/pipewire/extensions/client-node.h exists in both 'pipewire' and 'libpipewire'
/usr/include/pipewire-0.3/pipewire/extensions/metadata.h exists in both 'pipewire' and 'libpipewire'
/usr/include/pipewire-0.3/pipewire/extensions/profiler.h exists in both 'pipewire' and 'libpipewire'
/usr/include/pipewire-0.3/pipewire/extensions/protocol-native.h exists in both 'pipewire' and 'libpipewire'
/usr/include/pipewire-0.3/pipewire/extensions/session-manager.h exists in both 'pipewire' and 'libpipewire'
/usr/include/pipewire-0.3/pipewire/extensions/session-manager/impl-interfaces.h exists in both 'pipewire' and 'libpipewire'
/usr/include/pipewire-0.3/pipewire/extensions/session-manager/interfaces.h exists in both 'pipewire' and 'libpipewire'


seems like that split here was not done completely:
https://github.com/archlinux/svntogit-packages/commit/613f3176386e14d7115ced7361a2705fce41e3e5
Comment by Alex (BS86) - Monday, 20 February 2023, 19:59 GMT
tried clearing pacman cache, no dice, still getting this error (the list actually is a lot longer)
Comment by Henrique Custódio (henriqueffc) - Monday, 20 February 2023, 20:07 GMT
The same warnings appear when I go to upgrade.
Comment by Alex (BS86) - Monday, 20 February 2023, 20:11 GMT
looks like pipewire was reverted in testing but not the other packages:
Package (17) Old Version New Version Net Change

testing/alsa-card-profiles 1:0.3.66-1 1:0.3.66-2 0,00 MiB
testing/gst-plugin-pipewire 1:0.3.66-1 1:0.3.66-2 0,00 MiB
testing/harfbuzz 7.0.0-1 7.0.1-1 -0,16 MiB
testing/harfbuzz-icu 7.0.0-1 7.0.1-1 0,00 MiB
testing/iproute2 6.1.0-5 6.2.0-1 0,02 MiB
multilib-testing/lib32-harfbuzz 7.0.0-1 7.0.1-1 0,01 MiB
multilib-testing/lib32-libpipewire 1:0.3.66-2 0,71 MiB
multilib-testing/lib32-pango 1:1.50.12-1 1:1.50.13-1 0,00 MiB
multilib-testing/lib32-pipewire 1:0.3.66-1 1:0.3.66-2 -0,71 MiB
testing/libpipewire 1:0.3.66-2 1,79 MiB
extra/p7zip 1:17.04-4 1:17.05-1 0,00 MiB
testing/pango 1:1.50.12-1 1:1.50.13-1 0,00 MiB
extra/pipewire 1:0.3.66-1 1:0.3.65-6 0,34 MiB
testing/pipewire-alsa 1:0.3.66-1 1:0.3.66-2 0,00 MiB
testing/pipewire-audio 1:0.3.66-1 1:0.3.66-2 0,00 MiB
testing/pipewire-jack 1:0.3.66-1 1:0.3.66-2 0,00 MiB
testing/pipewire-pulse 1:0.3.66-1 1:0.3.66-2 0,00 MiB
Comment by Doug Newgard (Scimmia) - Monday, 20 February 2023, 20:16 GMT
fredbezies, that sounds like a partial update.

BS86, that is a different issue, and is valid. For some reason, pacman seems to want to downgrade the pipewire package.
Comment by Doug Newgard (Scimmia) - Monday, 20 February 2023, 20:19 GMT
Specifically doing pacman -Syu testing/pipewire works, something in the way pacman is handling this update is wrong.

It's almost certainly in the libprovides. Things depend on libpipewire-0.3.so, so pacman is trying to downgrade to the pipewire package that includes that instead of pulling in the new libpipewire package.
Comment by Henrique Custódio (henriqueffc) - Monday, 20 February 2023, 20:32 GMT
Scimmia, "pacman -Syu testing/pipewire" worked for me too.
Comment by Abdullah Al-Hasani (abdukabda) - Monday, 20 February 2023, 20:51 GMT
Had the same issue, solved by using 'pacman -Syu testing/pipewire'
Comment by Toolybird (Toolybird) - Monday, 20 February 2023, 21:34 GMT
Unsure if there is a bug here or not. Assigning to PM for a look.
Comment by Jan Alexander Steffens (heftig) - Monday, 20 February 2023, 21:37 GMT
I think this will resolve itself with the move to extra.
Comment by Jan Alexander Steffens (heftig) - Monday, 20 February 2023, 21:39 GMT
Moved. Fingers crossed that this indeed works. 🤞
Comment by Doug Newgard (Scimmia) - Monday, 20 February 2023, 21:46 GMT
It should work, but with the increased use of lib deps, it'll probably come up again. We should probably see if Allan will take a look to see if pacman is doing the right thing here, and if so, how can we avoid it.

Loading...