Your message dated Tue, 27 May 2025 09:06:53 +0000
with message-id <e1ujqgr-00czbe...@fasolo.debian.org>
and subject line Bug#1089933: fixed in llvm-toolchain-20 1:20.1.5-1~exp3
has caused the Debian Bug report #1089933,
regarding llvm-toolchain-19: allow multiple version of libc++* and libunwind*
to be installed at the same time
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1089933: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1089933
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: llvm-toolchain-19
Version: 1:19.1.4-1~deb12u1
Control: affects -1 chromium
Please make it so that libc++1-19 and subsequently ABI-versioned
packages (eg, libc++1-20) can be installed in parallel.
Rationale:
A few months ago, chromium switched to linking against (llvm's) libc++
instead of (gcc's) libstdc++. At the time, we were building on bookworm
using llvm 16. Because we are linking dynamically against libc++ (I'm
told that linking statically results in a segfault on armhf, by someone
who has tested it), the resulting chromium binary package has
dependencies upon libc++1-16, libc++abi1-16, and libunwind-16.
Chromium then switched to llvm 19, which resulted in dependencies upon
libc++1-19, libc++abi1-19, and libunwind-19. Because they contain the
same files (eg, all libunwind-* amd64 packages contain
/usr/lib/x86_64-linux-gnu/libunwind.so.1.0), the -16 and -19 versions of
the libraries conflict. This makes upgrading problematic, as various
package-related tooling will then either refuse to upgrade chromium.
'apt upgrade' and gnome-software will simply report the conflicts,
requiring an 'apt dist-upgrade' to get apt to remove libunwind-16 and
install libunwind-19. The conflict also means that multiple packages on
a system cannot be (dynamically) linked against multiple versions of llvm.
Request:
Ideally, libunwind-16 and libunwind-19 can be installed in parallel.
Likewise, libc++1-16 and libc++1-19. Since llvm 16 is being dropped from
sid/trixie, it would be good to get this fixed in llvm 19 and also
future major versions. We've already worked around the 16 -> 19 upgrade
issue for chromium by switching to (temporarily?) linking against libstdc++.
Proposal:
Assuming that newer versions of libc++* and libunwind-* symbols are
backwards compatible with older versions, it would be nice to rename the
packages based on their SONAMEs. For example, libc++1-19 becomes libc++1
(with libc++1 binary package being removed from the llvm-defaults source
package), and when a package builds against libc++-dev the resulting
binary package gets a dep of (libc++1 >= 1:19.1.5). That way, if some
other package links against libc++* from llvm20 while chromium links
against libc++* from llvm19, both packages can use libc++* from llvm20.
If they're not backwards compatible, I'm not really sure what to do. It
feels like the conflicting symlinks that are currently in libc++1-19
should instead be in llvm-default's libc++1 (which would allow the
conflicts to be dropped from libc++1-19), but we're not going to
backport llvm-defaults when we do a stable backport of llvm-toolchain-*.
Maybe that's good enough, though, and packages that want to use a
non-default llvm simply build using -Wl,-rpath,/usr/lib/llvm-19/lib ?
If anyone else has ideas, I'd love to hear them. I don't know how long
chromium will stick with libstdc++, and switching away from libc++ only
automatically cleans up older packages of libc++* during
unattended-upgrades but not via gnome-software or 'apt upgrade'.
OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: llvm-toolchain-20
Source-Version: 1:20.1.5-1~exp3
Done: Sylvestre Ledru <sylves...@debian.org>
We believe that the bug you reported is fixed in the latest version of
llvm-toolchain-20, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1089...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Sylvestre Ledru <sylves...@debian.org> (supplier of updated llvm-toolchain-20
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Tue, 27 May 2025 00:26:03 +0200
Source: llvm-toolchain-20
Architecture: source
Version: 1:20.1.5-1~exp3
Distribution: experimental
Urgency: medium
Maintainer: LLVM Packaging Team <pkg-llvm-t...@lists.alioth.debian.org>
Changed-By: Sylvestre Ledru <sylves...@debian.org>
Closes: 1089933
Changes:
llvm-toolchain-20 (1:20.1.5-1~exp3) experimental; urgency=medium
.
[ Andres Salomon ]
* Add libcxx-soname.diff to modify SONAMES for libc++1-20, libc++abi1-20,
and libuwind-20 to include the llvm major version (eg, 1.0.20 instead of
1.0).
* Remove conflicts/removes/provides from libc++1-20, libc++abi1-20, and
libunwind-20 to allow parallel package installation with other major
llvm versions (closes: #1089933).
Checksums-Sha1:
f862be96383b8e4a2e1432ac032a24d14eeed5cb 8416
llvm-toolchain-20_20.1.5-1~exp3.dsc
9918d35624a01cf3313509e4aec78792fa7aab05 155416
llvm-toolchain-20_20.1.5-1~exp3.debian.tar.xz
7ef59461749858eb800b1c998cdcbe9d06c8ae6b 40315
llvm-toolchain-20_20.1.5-1~exp3_amd64.buildinfo
Checksums-Sha256:
aea88b0ac6b1e4e31ecfd2c2714644f3571cd6ca4635abb586511db5d9cf0ab4 8416
llvm-toolchain-20_20.1.5-1~exp3.dsc
ef493c8ff4e5bc3587bf5ae3135052e0a1c90097041f0d3cd262db53e7c49479 155416
llvm-toolchain-20_20.1.5-1~exp3.debian.tar.xz
a34d974f2e2e7ad9415e83906c88ffb8c93e26505fd7e3fef06ba018f6ccedc7 40315
llvm-toolchain-20_20.1.5-1~exp3_amd64.buildinfo
Files:
0fb36f0b77732dda7d04c729e94d70f7 8416 devel optional
llvm-toolchain-20_20.1.5-1~exp3.dsc
83c4bb77f787ac08154d3d28b4c13bd0 155416 devel optional
llvm-toolchain-20_20.1.5-1~exp3.debian.tar.xz
b43bfe0560c45629421998d5171614ce 40315 devel optional
llvm-toolchain-20_20.1.5-1~exp3_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEtg21mU05vsTRqVzPfmUo2nUvG+EFAmg1dlgACgkQfmUo2nUv
G+GvrRAAlDgXGMS/Rx5jjjbvEnVgYsZOfl6jsi8htaFTZD/6ST1jDs9VDo4IPPtz
85GmDLQwtd7Q0J0JxLixQ+KFfIPzfUj3w6S9TXVnUpOAugcniEwL79lguyGo2RVo
yONWnwmCpvXOoeWWHsPOLYB6ifncrdFo5ewJe89SD6Vv7s4hy6MNFdCbWBoRdcSg
UYRuZoqkBB3SdeBwygIQRLWKTB7Nfn8O3w+fLDjMQ0qhdwLXGFW+tfkC+AwaCjls
ez00vGxmLyzt08pK6de27xBpRfClUxTSxAXixXtDW6FPFSqcZhq5JxF4jJR9Dvvx
RxmGiaqxV8McUG9D0a7WXwitFImX8mvMnHfU7zn0Q1vHswLfS8BloYqFsKxcKVGg
ldhmtzTfu8KALfsC3kelraKLM5hGh4e7vjUNlzazexy6/hnyWT3kTHy1fiqjI2n5
+41z+/Z7WBmCxhOtHB7sjse4/wfzxEnJuReaMnZ9ZqqhW5sKuk1Kn0MokrHjPv1t
GafK6wgW4uXCALPgeJdyq81WCpFGGDYHEPzJ8E6F2HwH0cUwSyG3Ix2nq1+KpGJT
0qCoOtdEt1O+Ns3kHnK6VheS3OHftJ1hL68CR/q0PCFOTHFaXvFYi5UPfcy5nM71
jKVLG9ApDuYM/KtS+BxpCM+suGcSNWJzbioTVxgc2k2SiCfqDhQ=
=t8/K
-----END PGP SIGNATURE-----
pgpexG1bTmizh.pgp
Description: PGP signature
--- End Message ---
