Hello Erich, Le dim. 22 janv. 2023 à 00:45, Erich Eickmeyer <eeickme...@ubuntu.com> a écrit : > > The introduction of the "Recommends: pipewire-alsa" line in the debian/control > file has reintroduced the problem resolved by bug #1020903 in which pipewire- > pulse is causing a conflict with pulseaudio, albiet indirectly this time. > > As pipewire-pulse is now soft-depending on pipewire-alsa, which does directly > conflict with pulseaudio. This is causing a package conflict, especialy when > seeded, when pulseaudio is installed and is causing the Ubuntu Studio seed to > fail to build. > > Ubuntu Studio was intending to include, in their built-in-house Studio > Controls > utility, a way to easily switch between the traditional Pulseaudio/JACK setup > and the Pipewire setup. Unfortunately, this recommends line, however well- > intentioned, completely broke that. > > My recommendation is to demote pulseaudio-alsa to a Suggests in this case. >
I removed pipewire-alsa from depends field of pipewire-pulse. Instead, I created a new metapackage pipewire-audio that depends on a set of pipewire packages recommended for a standard audio use of pipewire. A large part of bug reports against pipewire and wireplumber are mainly from users with broken config because they don't follow/install recommended packages. I guess this new package should make that clearer. I agree that pulseaudio and pipewire-pulse can be installed together at same time, but for whatever reasons several users have reported conflicts between them. And it seems easier (at least for standard users of pipewire for audio) to add a conflict between them, but I guess users of Ubuntu Studio don't have a standard use of pipewire. This brings me to the question, why do you want both pulseaudio and pipewire-pulse to be co-installable? Best regards, Dylan