FS#73427 - [pipewire-jack] conflicts with jack2 but doesn't provides?
Attached to Project:
Arch Linux
Opened by Matthew Armand (heylookmatt) - Thursday, 20 January 2022, 02:48 GMT
Last edited by Antonio Rojas (arojas) - Friday, 21 January 2022, 07:19 GMT
Opened by Matthew Armand (heylookmatt) - Thursday, 20 January 2022, 02:48 GMT
Last edited by Antonio Rojas (arojas) - Friday, 21 January 2022, 07:19 GMT
|
Details
Description:
The newest version of pipewire-jack (1:0.3.43-5) conflicts with jack2. However, it does not "provide" in the PKGBUILD jack2. It similarly conflicts with jack, and DOES provide jack. In its current state, upgrading pipewire-jack is impossible on a system currently using jack2: ``` :: pipewire-jack and jack2 are in conflict (jack). Remove jack2? [y/N] y error: failed to prepare transaction (could not satisfy dependencies) :: removing jack2 breaks dependency 'jack2' required by jack2-dbus ``` Is this the intended state/behavior? Should pipewire-jack also be providing jack2 so it can be a drop-in replacement? Or is there another recommended migration? Additional info: * package version(s): jack2 1.9.20-3, pipewire-jack 1:0.3.43-1 |
This task depends upon

I do see this commit now saying jack2-dbus is not supported, is
there any further documentation on this?
https://github.com/archlinux/svntogit-packages/commit/f6bdc1dba7121b747de920e166d62794c3a20ae4

I've found that the only package on my system which required
jack2-dbus was cadence, which I wasn't using frequently, so
removing that (and jack2-dbus) allowed the system update to
proceed. I'd still like to hear if there is any documentation on
either the Arch or Pipewire sides about this conflict.

You can find more info about that topic here:
https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/819

Got it, thanks Philip!