Bug#1081192: libllvm19: declares itself as MA: same but is not co-installable

[Simon McVittie]

Control: reopen 1081192
Control: found 1081192 1:19.1.0-3
Control: affects -1 + src:mesa

On Mon, 09 Sep 2024 at 09:57:01 +0000, Debian Bug Tracking System wrote:
> #1081192: libllvm19: declares itself as MA: same but is not co-installable
> [...] has been closed

This bug is still present in unstable (or, perhaps, present again in
unstable):

    Unpacking libllvm19:amd64 (1:19.1.0-3) ...
    dpkg: error processing archive /tmp/apt-dpkg-install-2k1zjW/03-libllvm19_1%3a19.1.0-3_amd64.deb (--unpack):
     trying to overwrite shared '/usr/lib/llvm-19/lib/libLLVM.so.19.1', which is different from other instances of package libllvm19:amd64

    $ dpkg -L libllvm19:i386
    ...
    /usr/lib/llvm-19/lib/libLLVM.so.19.1

Please test multiarch co-installability whenever this package is
restructured: as Sebastian said, this is important for a common use-case
of libllvm. On typical x86 machines, an easy way to do this is to have
the amd64 and i386 flavours co-installed, or if test-building for both
architectures takes a prohibitively long time, upload to experimental
after any restructuring of the package's contents and check that the
amd64 and i386 flavours from experimental are still co-installable before
re-uploading to unstable.

cc Mesa maintainers: similarly, please check for amd64/i386
co-installability before updating Mesa in unstable to a new version
of LLVM.

Thanks,
    smcv