Le 10/01/2025 à 12:33, Matthias Klose a écrit : > On 10.01.25 12:08, Emilio Pozuelo Monfort wrote: >> Control: clone -1 -2 >> Control: reassign -2 src:llvm-toolchain-19 >> Control: retitle -2 llvm-toolchain-19: readd gcn targets >> Control: block -1 with -2 >> >> Hi, >> >> On Thu, 12 Dec 2024 12:05:59 +0100 Matthias Klose <d...@debian.org> wrote: >>> On 12.12.24 00:07, Bastian Germann wrote: >>>> On Fri, 4 Oct 2024 18:50:41 +0200 Sylvestre Ledru >>> <sylves...@debian.org> > wrote: >>>>> We would like to remove llvm-toolchain-17 and this package uses >>> LLVM 17. >>>>> Please update to 19 (preferred) or 18 >>>> Please also get rid of the unnecessary llvm-* Build-Dependencies >>> when > updating the llvm version. >>> we can't do that unless we stop shipping GCC 13, or reverting the >>> removal of the gcn* targets in LLVM 18. So probably you should start >>> working on getting these targets back into LLVM 18 or LLVM 19. >> I don't see in the changelog for llvm 18 or 19 that the targets were >> removed, so perhaps the removal was unintentional? Sylvestre, can those >> be added back, so that amdgcn-tools can move to a newer llvm? This is >> one of the last blockers for the removal of llvm-toolchain-17 from trixie. > why is the removal required? There are no known security issues reported > (checked with the security team), and after an odyssey of the release > team blocking both llvm-18 and llvm-19 from testing for a long time, not > encouraging migration to newer LLVM versions, I don't see any necessity > to drop LLVM 17. If you want to drop one more version, please consider > dropping 18 instead.
Sorry but I am in favor of the llvm 17 removal. I don't see the point of removing 18 and keeping 17. Thanks Sylvestre
