Hello everyone,

Thank you, Adrian, for mentioning it. I'm the CERN engineer responsible for 
that migration. 

As of today, we should be covered by Trixie (LTS + ELTS). However, we would 
like to have the possibility of upgrading to Forky.

Having Forky support x86_64-v1 would give us a more modern system and a larger 
margin to both replace our x86_64-v1 hardware and cover the accelerator RUN 
(when beams will actually run).


Federico Vaga (CERN)

lunedì 7 settembre 2026 08:35, John Paul Adrian Glaubitz 
<[email protected]> ha scritto:

> Hi,
> 
> On Sun, 2025-10-26 at 13:21 +0100, Bastian Blank wrote:
> > Only three architectures set an explicit baseline in gcc-12 (Bookworm) and
> > gcc-15 (Forky):
> > * armhf: armv7-a+fp
> > * i386: i686
> > * s390: z196
> >
> > All other architectures use the default values.
> >
> > # Proposal for architecture baseline
> >
> > ## amd64 (and i386)
> >
> > * x86-64-v2: Supported since around 2008[^x86]. Used in RedHat 
> > 9[^redhat9x86].
> > * x86-64-v3: Supported since around 2013-2015[^x86]. Used in RedHat
> >   10[^redhat10].
> >
> > I propose to use the x86-64-v2 baseline in Forky.  It gives us more then 
> > the 15
> > years and everyone else already switched to it or even a newer variant.
> > Factoring in a possible LTS for Trixie, this means that x86-64-v1 will stop
> > being supported by Debian in 2030.
> 
> I'm very sorry to bring up this old thread again, but there is now a very
> good argument for keeping the baseline of the amd64 port at x86_64-v1, namely
> CERN.
> 
> They just started migrating their laboratory PCs away from RHEL to Debian
> because of the baseline switch in RHEL 9 and 10. They cannot just simply
> replace the hardware without making larger investments.
> 
> See: 
> https://www.ictjournal.ch/articles/2026-09-04/pourquoi-le-cern-choisit-debian-plutot-quun-renouvellement-materiel-a-54
> 
> Adrian
> 
> --
>  .''`.  John Paul Adrian Glaubitz
> : :' :  Debian Developer
> `. `'   Physicist
>   `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
> 
>

Reply via email to