From: Collin Funk <collin.funk1@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Colin Stagner <ask+git@howdoi.land>
Subject: Re: [PATCH] ci: avoid ubuntu:rolling in most jobs for now
Date: Thu, 05 Feb 2026 13:55:37 -0800 [thread overview]
Message-ID: <87bji2c0ti.fsf@gmail.com> (raw)
In-Reply-To: <xmqqy0l6khkd.fsf@gitster.g>
Junio C Hamano <gitster@pobox.com> writes:
> We just was hit by buggy uutils dirname in ubuntu:rolling.
> Avoid breakage caused by being on the bleeding edge.
>
> Signed-off-by: Junio C Hamano <gitster@pobox.com>
> ---
>
> * So here is what I have near the merge of "let's test contrib/
> stuff as well" in 'seen' for today's integration to avoid getting
> hit by broken dirname in ubuntu:rolling reported earlier in
>
> https://lore.kernel.org/git/ef128e1d-dd3e-4573-bfcd-6a98a0a1f394@howdoi.land/
>
> Until uutils used by ubuntu:rolling stabilizes a bit more, we may
> want to keep a patch like this in our CI jobs. Or we may offer
> ourselves as a guinea-pig? I do not have strong preference
> either way.
>
> .github/workflows/main.yml | 14 +++++++-------
> 1 file changed, 7 insertions(+), 7 deletions(-)
If you would prefer to keep using ubuntu:rolling, you can do something
like this:
$ podman run --rm -it ubuntu:25.10
$ dirname --version
dirname (uutils coreutils) 0.2.2
$ apt-get upgrade -y; apt-get update -y;
[...]
$ apt-get install -y coreutils-from-gnu coreutils-from-uutils- \
--allow-remove-essential
[...]
$ dirname --version | head -n 1
dirname (GNU coreutils) 9.5
I'm not familiar with the CI, so I am not voting for either option. I'll
let others decide. :)
Collin
next prev parent reply other threads:[~2026-02-05 21:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-05 21:26 [PATCH] ci: avoid ubuntu:rolling in most jobs for now Junio C Hamano
2026-02-05 21:55 ` Collin Funk [this message]
2026-02-06 7:39 ` Patrick Steinhardt
2026-02-07 4:27 ` Colin Stagner
2026-02-07 4:56 ` Junio C Hamano
2026-02-07 5:35 ` Colin Stagner
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=87bji2c0ti.fsf@gmail.com \
--to=collin.funk1@gmail.com \
--cc=ask+git@howdoi.land \
--cc=git@vger.kernel.org \
--cc=gitster@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