Matthias Klose <[email protected]> writes: > On 9/14/26 10:14, Simon Josefsson wrote: >> Hi >> I noticed packages depending on clang-19 have been triggered for >> autoremoval now. I want to update tillitis-tkey-libs and >> tillitis-tkey-device-signer to use a newer clang. >> But which version of clang? >> Testing has clang 21, 22 and unstable also have 23. >> Has it been decided what forky will ship with? > > I can't say anything about the default clang version, however I will > maintain LLVM 21 for forky, because it's used by the GCC offloading, > and for the python just-in-time feature. > > I have already got the approval from the security team, that shipping > multiple LLVM versions is not an issue from their side.
Thanks. Out of curiosity, why doesn't 22 or 23 solve your problem? Are you or someone else planning to maintain clang 22 or 23 for forky? Maybe pinning to 21 is actually okay then, since that's what the experimental upload I did already do, and hopefully I get the exact same binary output when rebuilt for unstable now. /Simon > Last year I also introduced some build profiles for LLVM, so some > packages could also be dropped if necessary (e.g. the -win package). > > Matthias > >
signature.asc
Description: PGP signature
