Re: [PATCH] ci: bump debian-11 job to debian-12

On Sun, Sep 06, 2026 at 11:11:37AM -0400, Jeff King wrote:

On Sat, Sep 05, 2026 at 09:58:22AM -0400, Jeff King wrote:

quoted

I started looking at this because I got an apt failure on a debian-11
job today. It might have just been a transient mirror failure (although
it reproduced for several minutes afterwards). But this seems like the
right step forward anyway.

BTW, I noticed that the linux32 build is using ubuntu 20.04, which has
been out of LTS for a year. But bumping isn't really an option; they
dropped i386 platform support, and so has Debian.

I'm mostly inclined to leave it unless/until it starts creating
headaches. To some degree, if we cannot even find an image to test
again, it might not be an important enough platform to care about. But I
can also imagine there is a long tail of oddball 32-bit platforms that
Git does run on (like small ARM chips), and it's nice to at least have
some coverage. Possibly there's an ARM image we could use (looks like
armhf?).

I agree that in the best case we'd find an alternative that works on 32
bit. But as you say, the list of x86 distros that still have support for
32 bit is shrinking quite a bit these days.

One of the bigger distros that still supports it properly is Alpine
Linux. We already support it via linux-musl-meson, so it should be easy
enough to extend. In theory, we could even merge these two jobs into a
single job. We'd of course lose 32 bit glibc support, but that might be
fine.

We also seem to use 20.04 for linux-TEST-vars. On the surface there's no
reason it couldn't be using ubuntu-latest, though I think this may be
one of those cases where it's doing double duty as "test exotic configs"
and "test on an older platform". But might be worth bumping to the
oldest in-scope LTS.

Yeah, might be worth it. It would've been great if they had a tag for
this so we odn't have to bump ourselves, but on the other hand it's only
a small bit of churn.

Patrick