Control: tags -1 forky On Sat, Mar 15, 2025 at 05:00:21PM -0400, Jeremy Bícha wrote: >... > llvm-defaults says that the default llvm-toolchain for Trixie is > llvm-toolchain-19. The Debian Release Team strongly prefers that there > be as few llvm-toolchain versions in Debian as possible. > > opencl-clang-17 uses llvm-toolchain-17 while opencl-clang-19 uses > llvm-toolchain-19. > > opencl-clang-17 has no reverse dependencies in Debian; therefore, > shouldn't it be removed now?
On Sat, Mar 15, 2025 at 05:00:25PM -0400, Jeremy Bícha wrote: >... > opencl-clang-18 has no reverse dependencies in Debian; therefore, > shouldn't it be removed now? >... What is the benefit of removing random leaf packages when the stated goal is impossible? While it is true that the release team prefers to have as few llvm-toolchain versions in a release as possible, you are far too late for that unless the freeze gets postponed. Both llvm-toolchain-17 and llvm-toolchain-18 are key packages, changing that would be the starting point. Open MPI and two gcc versions are among the packages that keep llvm-toolchain-17 in trixie. If the release team wanted to remove llvm-toolchain-18 from trixie, the main work would be to transition ghc to a different LLVM version. As soon an older LLVM version is no longer a key packages, autoremovals would automaticlly remove leaf packages like opencl-clang-* together with this LLVM version. > Thank you, > Jeremy Bícha cu Adrian
