Many Python packages were flagged for autoremoval recently as a result
of RC bugs in llvm-toolchain-19 and spirv-llvm-translator-19. It seems
like removal of these packages will likely require some coordination, so
I'm opening this tracking bug. The main places where action would be
needed if we want to remove LLVM 19 seem to be the GPU computation
ecosystem (especially, but not exclusively, CUDA in contrib) and the D
language ecosystem, plus some individual packages like justbuild.
It isn't immdiately clear to me why packages like for example
<https://tracker.debian.org/pkg/python-isoduration> have a dependency on
llvm-toolchain-19 and spirv-llvm-translator-19, and therefore are up for
autoremoval?
On the developer-accessible archive mirror on coccia, if I run the
command below to simulate removal of llvm-toolchain-19,
spirv-llvm-translator-19 and packages that depend on them, dak tells me
that the only broken (Build-)Depends are for source packages in contrib
(which are not eligible to be Depends or Build-Depends for a package in
main), plus the old "cruft" version of libosmesa6 from src:mesa (which I
believe is already not in testing, and can be removed from unstable if
the archive team does #1147651 and #1147652 first). So I'm unsure why
packages like python-isoduration are affected. Can someone clarify?
Thanks,
smcv
----
dak rm -R -n \
amdgcn-tools-19 \
cccl \
cheesecutter \
dcontainers \
dh-dlang \
diet-ng \
dlang-libevent \
dlang-openssl \
dub \
gir-to-d \
glib-d \
gtk-d \
justbuild \
ldc \
llvm-toolchain-19 \
mir-core \
mustache-d \
nvidia-cuda-toolkit \
onedrive \
opencl-clang-19 \
pytorch-cuda \
sambamba \
spirv-llvm-translator-19 \
stdgpu \
stdgpu-contrib \
tilix \
tillitis-tkey-device-signer \
tillitis-tkey-libs \
tkey-ssh-agent \
${NULL+}