From: Patrick Steinhardt <ps@pks.im>
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: Fri, 6 Feb 2026 08:39:54 +0100 [thread overview]
Message-ID: <aYWaytvnR8wOdc1s@pks.im> (raw)
In-Reply-To: <xmqqy0l6khkd.fsf@gitster.g>
On Thu, Feb 05, 2026 at 01:26:42PM -0800, Junio C Hamano wrote:
> 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.
I think being a guinea-pig and reporting any issues we find to upstream
would be the best outcome. It's feasible that eventually, Ubuntu may
fully switch over to uutils, and if that's the case it would be great if
we had already ironed out all the bugs that we happen to hit ourselves.
So I think demoting to "latest" is a fine intermediate step to fix our
CI, but ideally we'd do a similar workaround to the sudo.ws workaround
we have in "ci/install-dependencies.sh" so that we only disable the
pieces that _don't_ work. That'd make it easy to contiue using the parts
that _do_ work, and once the bug has been fixed upstreamed and has
become part of Ubuntu we can then disable the workaround.
I plan to have a deeper look at our CI next week anyway to fix some
small warts and a test failure that we hit on GitLab with the MSVC job.
So maybe we commit your fix as an intermediate step, and I'll then
revert it and come up with a more localized fix?
Thanks!
Patrick
next prev parent reply other threads:[~2026-02-06 7:40 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
2026-02-06 7:39 ` Patrick Steinhardt [this message]
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=aYWaytvnR8wOdc1s@pks.im \
--to=ps@pks.im \
--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