[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#969612: krfb: please transition to pipewire 0.3, initially in experimental



Control: tags -1 + patch

On Sun, 06 Sep 2020 at 00:02:46 +0100, Simon McVittie wrote:
> pipewire 0.3 has now hit experimental. As discussed in #966535 and
> on #debian-kde, the first step for transition #966535 is to make sure
> the few packages that currently B-D on pipewire 0.2 can be recompiled
> with 0.3. It would be great if you could do this in experimental soon
> (please close this bug with that upload), and either be ready to re-upload
> to unstable when the transition starts, or accept a 0-day NMU with the
> same change.

This builds successfully:
https://salsa.debian.org/qt-kde-team/kde/krfb/-/merge_requests/2

I haven't tested it beyond sbuild succeeding: I don't use KDE myself, so I
don't know how the pieces fit together.

If it's anything like GNOME, then it might not be possible to actually
*use* the functionality provided by this PipeWire dependency until a
sufficiently new version of kwin has been built with PipeWire support
enabled, in which case the only testing that is required would be to
check that it doesn't cause regressions for things that already work -
but perhaps the "shape" of the KDE stack is sufficiently different that
it doesn't need PipeWire in the compositor like GNOME does.

    smcv


Reply to: