Bug#969613: xdg-desktop-portal-kde: please transition to pipewire 0.3, initially in experimental
Control: tags -1 + patch
On Sun, 06 Sep 2020 at 00:08:08 +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.
>
> My next upload of xdg-desktop-portal to experimental will enable the
> pipewire 0.3 dependency. You might not be able to test this functionality
> in x-d-p-kde until I've done that (I'm not completely clear on how the
> screencasting/remote desktop portal works).
xdg-desktop-portal is now on its way to experimental.
> Because x-d-p-kde has different versions in unstable and experimental,
> it would also be great if someone from the KDE team could test a rebuild
> of the x-d-p-kde from unstable that has been rebuilt against pipewire
> 0.3 and report back whether it works. Unfortunately you won't be able to
> upload that to Debian immediately, because we only have one instance of
> experimental, and for this particular source package it's already in use.
If the version in experimental is ready for release to bullseye, it
would probably be best to use that one for this transition. Making it
build against PipeWire 0.3 is straightforward:
https://salsa.debian.org/qt-kde-team/kde/xdg-desktop-portal-kde/-/merge_requests/6
Or if you would prefer to keep the version in unstable and apply minimal
fixes, it needs at least the FindPipeWire.cmake patches from
https://salsa.debian.org/qt-kde-team/kde/xdg-desktop-portal-kde/-/merge_requests/5
and maybe the fixes to the C++ code too (taken from upstream release
v5.18.1).
In both cases, as with krfb, I have built the package successfully in
sbuild but not otherwise tested it. I don't know how the components of KDE
fit together, so I don't know whether the PipeWire integration is
practically useful without having a version of kwin that also has PipeWire
integration.
If PipeWire integration is not testable in Debian yet, then it will be
necessary to either upload it untested, or disable it until enough of the
stack is in place that it can be tested. Either is fine from the point of
view of this transition.
Thanks,
smcv
Reply to: