From: "Ludovic Courtès" <ludo@gnu.org>
To: Guix Devel <guix-devel@gnu.org>
Subject: Re: Release progress, week 6
Date: Mon, 21 Nov 2022 11:04:05 +0100 [thread overview]
Message-ID: <87edtwmxnu.fsf@gnu.org> (raw)
In-Reply-To: <Y3aVtaben9qPxJz1@3900XT> (Efraim Flashner's message of "Thu, 17 Nov 2022 22:12:37 +0200")
Hi,
Efraim Flashner <efraim@flashner.co.il> skribis:
> On Thu, Nov 17, 2022 at 05:04:43PM +0100, Ludovic Courtès wrote:
[...]
>> - i586-gnu: as proposed last week, I’ll drop i586-gnu from
>> ‘etc/release-manifest.scm’.
>>
>> - armhf-linux: Mathieu re-queued a number of armhf-linux builds
>> since last week but that hasn’t had a visible effect so far.
>>
>> - aarch64-linux: Little progress: Emacs is now available on ci.guix
>> but it’s not clear while the others aren’t showing up, even after
>> restarting them in the Cuirass interface.
>>
>> It would seem that a lot of aarch64 builds are queued but not
>> getting processed. Any idea how to investigate that, Mathieu?
>>
>> - powerpc64le-linux: No progress.
>
> Can we bypass cuirass building the packages and from Berlin ask for the
> packages to be built? Then it'll offload to the appropriate machine and
> should show up faster for make assert-binaries-available.
Yes, I shamelessly ended up doing that: running “guix build” on berlin
to fill in the gaps. :-)
Ludo’.
next prev parent reply other threads:[~2022-11-21 10:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-17 16:04 Release progress, week 6 Ludovic Courtès
2022-11-17 20:12 ` Efraim Flashner
2022-11-21 10:04 ` Ludovic Courtès [this message]
2022-11-18 19:52 ` Mathieu Othacehe
2022-11-21 10:02 ` Ludovic Courtès
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87edtwmxnu.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).