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?

What could be said about when (and how) that decision will be made?

I don't want to do multiple jumps for these Tillitis packages.  On every
compiler bump, the device owner of a Tillitis key gets a new private key
when the firwmare changes.  That has a cost, people have to change SSH
authorized_keys etc.  So if we haven't decided on clang version yet, I
would tentatively prefer for the autoremoval to succeed rather than
pollute the ecosystem with a growing number of incompatible unique
Tillitis firmwares.  There should not be any functional changes to the
firmware depending on if it is compiled with clang 19, 21, 22 or 23.  I
did an upload to experimental moving to clang 21 because of #1124050 and
#1124063 but given that both clang 22 and 23 are now in unstable, I'm
wondering if that was a good idea.  Fortunately that was for
experimental, so could be considered non-supported anyway.

/Simon

Attachment: signature.asc
Description: PGP signature

Reply via email to