Package: libroc0.4
Version: 0.4.0+dfsg-4+b1
Severity: wishlist
libroc has libunwind integration, which seems to be limited to using it
to print better backtraces on a fatal signal or assertion failure.
While nice to have, this doesn't seem hugely important: under normal
circumstances, libroc shouldn't be crashing, and if it crashes due to
a bug, tools like systemd-coredump are a more reliable way to get
high-quality backtraces (without requiring the crashing process to still
be in a mostly-working state).
Meanwhile, libunwind has several unaddressed RC bugs, including a build
failure on i386 that causes it to be out-of-sync between amd64 and i386.
This makes it difficult for users of unstable to have working Pipewire
for both amd64 and i386 processes, because Pipewire libraries depend on
libroc and therefore indirectly libunwind8, and apt/dpkg requires
the version number of libunwind8 to be the same for amd64 and i386.
Would it be possible to disable the libunwind integration in libroc,
either on i386 or on all architectures?
Thanks,
Simon
