From: Junio C Hamano <gitster@pobox.com>
To: "brian m. carlson" <sandals@crustytoothpaste.net>
Cc: git@vger.kernel.org, Taylor Blau <me@ttaylorr.com>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: [RFH] GitHub deprecates Ubuntu 20.04 Actions runner image
Date: Tue, 08 Apr 2025 15:30:30 -0700 [thread overview]
Message-ID: <xmqqcydmuvzt.fsf@gitster.g> (raw)
In-Reply-To: <Z_WagT6zeeQGNa0k@tapette.crustytoothpaste.net> (brian m. carlson's message of "Tue, 8 Apr 2025 21:52:01 +0000")
"brian m. carlson" <sandals@crustytoothpaste.net> writes:
>> It appears that Dscho (CC'ed) is futzing with the generation of
>> sparse package on Ubuntu 20.04 and 22.04 and getting affected
>> by the same 20.04 brownout
>>
>> https://dev.azure.com/git/git/_build/results?buildId=2396&view=results
>>
>> so probably I do not have to worry about it and let Dscho take
>> care of the whole thing?
> ...
>> @@ -457,9 +457,9 @@ jobs:
>> with:
>> repository: git/git
>> definitionId: 10
>> - artifact: sparse-20.04
>> + artifact: sparse-22.04
>> - name: Install the current `sparse` package
>> - run: sudo dpkg -i sparse-20.04/sparse_*.deb
>> + run: sudo dpkg -i sparse-22.04/sparse_*.deb
>
> I don't know how these are generated, but this seems like a good start
> to try and we can adjust it later on if there's more moving parts to
> fix.
I think mails crossed among three of us.
<77f82414-261c-d2bc-f911-ed3d4b06c86e@gmx.de>
prev parent reply other threads:[~2025-04-08 22:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-08 20:16 [RFH] GitHub deprecates Ubuntu 20.04 Actions runner image Junio C Hamano
2025-04-08 21:52 ` brian m. carlson
2025-04-08 22:30 ` 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=xmqqcydmuvzt.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=me@ttaylorr.com \
--cc=sandals@crustytoothpaste.net \
/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.