Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.bugs.dist > #1092715

Bug#997818: Still present in 0.4.8-2 and other packaging issues

From Diederik de Haas <didi.debian@cknow.org>
Newsgroups linux.debian.bugs.dist
Subject Bug#997818: Still present in 0.4.8-2 and other packaging issues
Date 2022-02-10 22:50 +0100
Message-ID <DPpu9-WiY-3@gated-at.bofh.it> (permalink)
References <Dc5yx-5HS-11@gated-at.bofh.it>
Organization Connecting Knowledge

Show all headers | View raw


[Multipart message — attachments visible in raw view] - view raw

Control: found -1 0.4.8-2

First I'll describe what I tried to do and I'll attach the console output (as 
it's rather long), so you can see what exactly I did.

I'm setting up a Rock64 device (arm64) cleanly with pipewire (so no PA which 
my 'soundserver' device was previously running), so I installed that and with 
it came pipewire-media-session as default recommended option of pipewire-bin.

Through the #pipewire IRC channel I understood that pipewire-media-session is 
'soon' to be actually deprecated with the release of wireplumber 0.4.8, so I 
figured I'd best switch now as I still need to setup/configure the device.

That's when I ran into this issue.
It didn't seem to be marked as a fatal flaw, so it appears that it concluded 
the install ... but in what exact state it is in  ... I do not know.
That device has 'bookworm' configured as default release, but sid is also 
available.

As I wanted the 0.4.8-2 version, I then upgraded wireplumber to the sid 
version, which ones again produced the error of this bug report. It however 
did not also upgrade libwireplumber-0.4-0, which I expect it should?
IOW: should there be a (more) tight version dependency between those?

As I didn't like the unknown state that device was in wrt pipewire/
wireplumber, I purged both packages with the plan to then install pipewire and 
wireplumber together (explicitly), so it would not install 
pipewire-media-session and I expected that I would not run into this issue.
That turned out to be an incorrect expectation as the previous purge didn't 
clean up things in /etc/systemd/user/ which still contains 3 symlinks which 
point to /dev/null and one link which points to /usr/lib/systemd/user/
pipewire-media-session.service ... which doesn't exist (anymore).
There's also a /etc/systemd/user/pipewire.service.wants/ directory, which 
contains the same link to that non-existing file and a link to 
/usr/lib/systemd/user/wireplumber.service which also didn't exist anymore 
(after another purge, in this case of both pipewire and wireplumber)

AFAIK a purge should cleaned it all up and 'aptitude install wireplumber 
pipewire' should've succeeded (cleanly), but it did not.
I think the priority of this bug should be increased to possibly RC level as 
otherwise many more systems will end up with a 'broken' pipewire/wireplumber/
pipewire-media-session configuration which will make it more difficult to 
'recover' from.
And if I did understand correctly that with wireplumber 0.4.8 it should 
actually replace pipewire-media-session, it may also be a good idea to reverse 
the optional recommends so that wireplumber does get installed by default now.

Cheers,
  Diederik

Back to linux.debian.bugs.dist | Previous | Next — Next in thread | Find similar | Unroll thread


Thread

Bug#997818: Still present in 0.4.8-2 and other packaging issues Diederik de Haas <didi.debian@cknow.org> - 2022-02-10 22:50 +0100
  Bug#997818: Still present in 0.4.8-2 and other packaging issues Diederik de Haas <didi.debian@cknow.org> - 2022-02-10 23:40 +0100

csiph-web