Bug#1140179: transition: openssl

On 2026-06-17 01:40:33 [+0300], Adrian Bunk wrote:
> On Tue, Jun 16, 2026 at 11:22:45PM +0200, Sebastian Andrzej Siewior wrote:
> >...
> > The longterm plan is to switwch to 4.0 and then to 4.2 which should be
> > released around April and will be LTS. So Forky would have an LTS
> > supported release, see
> > 	https://openssl-library.org/post/2026-05-07-future-release/
> >...
> 
> Does the Release Team commit to the forky toolchain freeze being after 
> April 2027?

> The alternative would be to defer this transition to duke and downgrade 
> forky to 3.5 (same as in trixie), which is an LTS release supported 
> until April 2030.

That is the motivation I need.
I would prefer to have the 4.2 LTS series in the upcoming release. Given
the amount of PQC code and the status of quantum computing I would
strongly prefer to get the stack ready.
Looking back at recent releases, the fallout between 3.[0…6] was small if
it all and limited to a few packages as far as I remember. The debci
caught reported them "early".

> This is not a one-off issue:
> OpenSSL plans to have new LTS releases every second year in April,
> always in our release years.
> 
> cu
> Adrian

Sebastian