# emerge -pvq =media-video/pipewire-1.2.0 [ebuild U ] media-video/pipewire-1.2.0 [1.0.7] USE="X bluetooth dbus doc echo-cancel extra ffmpeg flatpak gsettings gstreamer jack-client liblc3 lv2 man readline roc ssl systemd v4l zeroconf -ieee1394 -jack-sdk -modemmanager -pipewire-alsa (-selinux) -sound-server (-system-service) -test" ABI_X86="32 (64) (-x32)"
Created attachment 896626 [details] build.log.xz
Ah, yeah. We should conditionalise it on USE=sound-server.
Upstream commit implementing an option whether to install this conflicting file: https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/bd87902da6a2badae096e4679eedfe9da2e75d79 The builtin default is type: 'feature', value: 'auto') and the file is only installed based on: if get_option('gsettings-pulse-schema').enabled() So you should have to explicitly pass =enabled to install it, which we don't do and which isn't in your log.
Did you look at the wrong part of the log? Remember that it's multilib. > -Dgsettings=enabled -Dgsettings-pulse-schema=enabled
I thought I grepped the whole thing...
Fun.
Okay, I am now able to reproduce this locally via USE="gsettings bluetooth". Patch accepted upstream to break the accidental USE=gsettings overwriting by USE=-bluetooth. Fixing the file conflict is a bit messy since there's no query function to check when two USE flags are set together.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f91e6697fba4b081fff1cc188040c34aee59ea58 commit f91e6697fba4b081fff1cc188040c34aee59ea58 Author: Eli Schwartz <eschwartz93@gmail.com> AuthorDate: 2024-06-30 15:36:54 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2024-07-01 08:19:12 +0000 media-video/pipewire: fix file conflicts with pulseaudio-daemon We don't *have* to be replacing it as the sound server, that's why a USE flag exists for precisely that. But pipewire 1.2.0+ offers to install files from pulseaudio-daemon on the theory it can be replacing it... which means we need to tell it not to do so when USE="-sound-server". Previously, we installed this whenever gsettings was enabled, even though its purpose was to enable API usage independent of being the main sound server. Closes: https://bugs.gentoo.org/935139 Signed-off-by: Eli Schwartz <eschwartz93@gmail.com> Signed-off-by: Sam James <sam@gentoo.org> media-video/pipewire/pipewire-1.2.0.ebuild | 11 ++++++++++- media-video/pipewire/pipewire-9999.ebuild | 11 ++++++++++- 2 files changed, 20 insertions(+), 2 deletions(-) Additionally, it has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b30d06275a07b58afce9912aafaa86d28bd5985e commit b30d06275a07b58afce9912aafaa86d28bd5985e Author: Eli Schwartz <eschwartz93@gmail.com> AuthorDate: 2024-06-30 20:33:56 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2024-07-01 08:19:13 +0000 media-video/pipewire: fix automagic USE=gsettings when USE=bluetooth And the reverse. If USE="-bluetooth", the gsettings detection gets reset to not-found. Bug: https://bugs.gentoo.org/935139 Signed-off-by: Eli Schwartz <eschwartz93@gmail.com> Signed-off-by: Sam James <sam@gentoo.org> .../files/pipewire-1.0.7-automagic-gsettings.patch | 80 ++++++++++++++++++++++ .../files/pipewire-1.2.0-automagic-gsettings.patch | 79 +++++++++++++++++++++ media-video/pipewire/pipewire-1.0.7.ebuild | 2 + media-video/pipewire/pipewire-1.2.0.ebuild | 2 + 4 files changed, 163 insertions(+)
