Le jeu. 4 nov. 2021 à 16:11, Michael Biebl a écrit :
>
> Yeah, see https://github.com/mesonbuild/meson/issues/1602
> That said, maybe pipewire want's to borrow from systemd here:
>
> https://github.com/systemd/systemd/blob/main/tools/meson-make-symlink.sh
> https://github.com/systemd/systemd/blob/
On 04.11.21 15:42, Dylan Aïssi wrote:
Le jeu. 4 nov. 2021 à 14:57, Michael Biebl a écrit :
I guess we could just as well ship a symlink
/usr/bin/pipewire-pulse → /usr/bin/pipewire ?
Dylan, do you know why upstream basically builds the same executable twice?
Thanks! :-) Indeed, I got the cl
Le jeu. 4 nov. 2021 à 14:57, Michael Biebl a écrit :
>
> I guess we could just as well ship a symlink
> /usr/bin/pipewire-pulse → /usr/bin/pipewire ?
>
>
> Dylan, do you know why upstream basically builds the same executable twice?
Thanks! :-) Indeed, I got the clarification, both are the same bi
I briefly looked into this.
The offending binares are /usr/bin/pipewire and /usr/bin/pipewire-pulse
On amd64 I get:
# objdump -g pipewire-pulse | tail -n 5
Contents of the .gnu_debuglink section (loaded from pipewire-pulse):
Separate debug info file: aecb16cbc8f77084957492db3828061b543732
Processing control commands:
> tags -1 help
Bug #998126 [src:pipewire] pipewire-pulse-dbgsym: dbgsym files overlap between
packages
Added tag(s) help.
--
998126: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998126
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 help
Hi,
Le sam. 30 oct. 2021 à 21:09, Martin-Éric Racine
a écrit :
>
> Selecting previously unselected package libpipewire-0.3-0-dbgsym:i386.
> (Reading database ... 127295 files and directories currently installed.)
> Preparing to unpack .../libpipewire-0.3-0-dbgsym_0.3.39-3_i
6 matches
Mail list logo
