All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Phillip Wood <phillip.wood123@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: CI Failures
Date: Fri, 14 Nov 2025 12:22:53 -0800	[thread overview]
Message-ID: <xmqqv7jcgy8y.fsf@gitster.g> (raw)
In-Reply-To: <b1775e1a-4f6c-4116-9587-69526d379b42@gmail.com> (Phillip Wood's message of "Fri, 14 Nov 2025 20:11:13 +0000")

Phillip Wood <phillip.wood123@gmail.com> writes:

> On 14/11/2025 20:00, Phillip Wood wrote:
>> I'm seeing all the Ubuntu based jobs fail. Judging by the error messages 
>> at [1] it appears that their version of sudo no longer supports "-- 
>> preserve-env" which breaks all of our scripts. Does anyone know how to 
>> make sure we install the C version of sudo rather than the rust version? 
>> Failing that I guess we could switch to using "runuser"
>
> Sorry for the noise, I see this was fixed last month, I had accidentally 
> rebased onto a stale branch.

I think we've merged the fix down to the maint-2.51 track but not to
maint-2.50 and below.  fddb4842 (ci: fix broken jobs on Ubuntu 25.10
caused by switch to sudo-rs(1), 2025-10-10) cannot be merged below
there, but you should be able to cherry-pick if needed.


  reply	other threads:[~2025-11-14 20:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-14 20:00 CI Failures Phillip Wood
2025-11-14 20:11 ` Phillip Wood
2025-11-14 20:22   ` Junio C Hamano [this message]
2025-11-14 20:34     ` CI Failures (osx with p4) Junio C Hamano
2025-11-16 15:23       ` Koji Nakamaru
2025-11-16 17:18         ` Junio C Hamano
2025-11-16 23:25           ` Koji Nakamaru
2025-11-17  0:25             ` Junio C Hamano
  -- strict thread matches above, loose matches on Subject: below --
2025-08-12  7:56 CI failures Morten Brørup

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=xmqqv7jcgy8y.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=phillip.wood123@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.