From: Junio C Hamano <gitster@pobox.com>
To: Todd Zullinger <tmz@pobox.com>
Cc: Patrick Steinhardt <ps@pks.im>,
git@vger.kernel.org, Jeff King <peff@peff.net>
Subject: Re: [PATCH 4/8] ci: switch away from unsupported i386/ubuntu image
Date: Thu, 08 Oct 2026 11:12:11 -0700 [thread overview]
Message-ID: <xmqq4iew12pw.fsf@gitster.g> (raw)
In-Reply-To: <20261008150336.CzZS-oEZ@teonanacatl.net> (Todd Zullinger's message of "Thu, 8 Oct 2026 11:03:36 -0400")
Todd Zullinger <tmz@pobox.com> writes:
> Patrick Steinhardt wrote:
>> The linux32 job is used to exercise Git on a 32 bit platform. That job
>> uses i386/ubuntu:20.04 though, and that version of Ubuntu is end of life
>> nowadays. Furthermore, Ubuntu has dropped support for 32 bit entirely
>> with the 20.04 release, so we cannot easily upgrade it to a more recent
>> image anymore.
>
> Should "with the 20.04 release" be 22.04 (or whatever
> release dropped i386)?
FWIW, I read the above to mean "32bit support, together with 20.04,
are now gone", and did not feel any need for rephrasing. But
reading it again, yes, it can be read both ways.
Ubuntu has dropped support for 32-bit entirely, together with
20.04 release, so upgrading it to a more recent image would not
help us keeping 32-bit support.
perhaps?
next prev parent reply other threads:[~2026-10-08 18:12 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-08 10:01 [PATCH 0/8] ci: some housekeeping and modernizations Patrick Steinhardt
2026-10-08 10:01 ` [PATCH 1/8] t5004: skip SHA-1-only test in SHA-256 repository Patrick Steinhardt
2026-10-08 18:05 ` Junio C Hamano
2026-10-09 5:46 ` Patrick Steinhardt
2026-10-08 10:01 ` [PATCH 2/8] ci: fix "fedora-breaking-changes-meson" job Patrick Steinhardt
2026-10-08 10:01 ` [PATCH 3/8] ci: drop unused "linux-clang" logic Patrick Steinhardt
2026-10-08 10:01 ` [PATCH 4/8] ci: switch away from unsupported i386/ubuntu image Patrick Steinhardt
2026-10-08 15:03 ` Todd Zullinger
2026-10-08 18:12 ` Junio C Hamano [this message]
2026-10-09 5:46 ` Patrick Steinhardt
2026-10-08 10:01 ` [PATCH 5/8] ci: rename linux-TEST-vars job Patrick Steinhardt
2026-10-08 10:01 ` [PATCH 6/8] ci: switch away from EOL'd Ubuntu version in linux-exotic Patrick Steinhardt
2026-10-08 10:01 ` [PATCH 7/8] ci: drop now-dead Python 2 coverage Patrick Steinhardt
2026-10-08 10:01 ` [PATCH 8/8] ci: drop redundant linux-reftable job Patrick Steinhardt
2026-10-08 18:18 ` Junio C Hamano
2026-10-09 5:55 ` Patrick Steinhardt
2026-10-09 20:22 ` Junio C Hamano
2026-10-09 11:31 ` [PATCH v2 0/8] ci: some housekeeping and modernizations Patrick Steinhardt
2026-10-09 11:31 ` [PATCH v2 1/8] t5004: skip SHA-1-only test in SHA-256 repository Patrick Steinhardt
2026-10-09 11:31 ` [PATCH v2 2/8] ci: fix "fedora-breaking-changes-meson" job Patrick Steinhardt
2026-10-09 11:32 ` [PATCH v2 3/8] ci: drop unused "linux-clang" logic Patrick Steinhardt
2026-10-09 11:32 ` [PATCH v2 4/8] ci: switch away from unsupported i386/ubuntu image Patrick Steinhardt
2026-10-09 11:32 ` [PATCH v2 5/8] ci: rename linux-TEST-vars job Patrick Steinhardt
2026-10-09 15:31 ` SZEDER Gábor
2026-10-09 11:32 ` [PATCH v2 6/8] ci: switch away from EOL'd Ubuntu version in linux-exotic Patrick Steinhardt
2026-10-09 11:32 ` [PATCH v2 7/8] ci: drop now-dead Python 2 coverage Patrick Steinhardt
2026-10-09 11:32 ` [PATCH v2 8/8] ci: improve reftable test coverage Patrick Steinhardt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqq4iew12pw.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=ps@pks.im \
--cc=tmz@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox