Git development
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Harald Nordgren via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org,  Harald Nordgren <haraldnordgren@gmail.com>
Subject: Re: [PATCH 0/3] ci: fix jobs failing on Ubuntu 26.04
Date: Tue, 03 Nov 2026 14:04:39 -0800	[thread overview]
Message-ID: <xmqqse1h4lmw.fsf@gitster.g> (raw)
In-Reply-To: <pull.2478.git.git.1793530936.gitgitgadget@gmail.com> (Harald Nordgren via GitGitGadget's message of "Sun, 01 Nov 2026 11:02:13 +0000")

"Harald Nordgren via GitGitGadget" <gitgitgadget@gmail.com> writes:

> Four CI jobs fail since ubuntu-latest moved to Ubuntu 26.04.
>
>  * documentation, fuzz smoke test and static-analysis fail with ln: failed
>    to create symbolic link '/usr/bin/dirname': Already exists. Run the ln
>    with sudo.

I see this breakage.  Haven't they corrected the Rust rewrite of
dirname by now, by the way, to make this overwrite unnecessary yet?

>  * linux32 cannot resolve deb.debian.org. Pin it to ubuntu-24.04. The Docker
>    update in actions/runner-images#15205 fixes this on 26.04, but a new
>    runner image will take a long time to roll out, and CI should not stay
>    broken while we wait.

Sigh, but this one is rather straightforward.  We need to be aware
of this change so that we can revert it when it becomes unnecessary.

>  * Use apt-get in linux32 to get rid of the apt does not have a stable CLI
>    interface warnings.

I can see this well, but it is a warning only, so I do not know how
much value in addressing it would be.

> The first two are based on Johannes Schindelin's fixes in Git for Windows
> (git-for-windows/git#6473).
>
> Harald Nordgren (3):
>   ci: use apt-get in the linux32 job
>   install-dependencies: work around a permission problem
>   ci: pin linux32 to ubuntu-24.04 to restore networking

Will queue.  Thanks.

>
>  .github/workflows/main.yml | 6 ++++--
>  ci/install-dependencies.sh | 2 +-
>  2 files changed, 5 insertions(+), 3 deletions(-)
>
>
> base-commit: 50fe5cc63f9cd6e89b87a2c9ccf96a444f4cfdb7
> Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-2478%2FHaraldNordgren%2Fci-linux32-apt-get-v1
> Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-2478/HaraldNordgren/ci-linux32-apt-get-v1
> Pull-Request: https://github.com/git/git/pull/2478

      parent reply	other threads:[~2026-11-03 22:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-01 11:02 [PATCH 0/3] ci: fix jobs failing on Ubuntu 26.04 Harald Nordgren via GitGitGadget
2026-11-01 11:02 ` [PATCH 1/3] ci: use apt-get in the linux32 job Harald Nordgren via GitGitGadget
2026-11-01 11:02 ` [PATCH 2/3] install-dependencies: work around a permission problem Harald Nordgren via GitGitGadget
2026-11-01 11:02 ` [PATCH 3/3] ci: pin linux32 to ubuntu-24.04 to restore networking Harald Nordgren via GitGitGadget
2026-11-03 22:04 ` Junio C Hamano [this message]

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=xmqqse1h4lmw.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --cc=haraldnordgren@gmail.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