[Pkg-utopia-maintainers] Bug#998126: Bug#998126: pipewire-pulse-dbgsym: dbgsym files overlap between packages

[Michael Biebl]

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.debug
   CRC value: 0xc80d0d48

# objdump -g pipewire | tail -n 5
Contents of the .gnu_debuglink section (loaded from pipewire):

   Separate debug info file: aecb16cbc8f77084957492db3828061b543732.debug
   CRC value: 0xe4077046


Looking at src/daemon/meson.build I see

pipewire_exec = executable('pipewire',
   pipewire_daemon_sources,
   install: true,
   c_args : pipewire_c_args,
   include_directories : [configinc, spa_inc],
   dependencies : [pipewire_dep, ],
)

executable('pipewire-pulse',
   pipewire_daemon_sources,
   install: true,
   c_args : pipewire_c_args,
   include_directories : [configinc, spa_inc],
   dependencies : [pipewire_dep, ],
)


Basically, we build the same binary twice, the only difference is the 
executable name.

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?

The binary behaves differently when called with a different name, but a 
symlink would just as well do in this case.

Regards,
Michael
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-utopia-maintainers/attachments/20211104/6c899499/attachment.sig>