From: "Ludovic Courtès" <ludo@gnu.org>
To: Christopher Baines <mail@cbaines.net>
Cc: "Andreas Enge" <andreas@enge.fr>,
72959@debbugs.gnu.org, 宋文武 <iyzsong@envs.net>
Subject: [bug#72959] Request for merging "fonts-split-outputs" branch
Date: Tue, 15 Oct 2024 17:40:01 +0200 [thread overview]
Message-ID: <875xptxtm6.fsf@gnu.org> (raw)
In-Reply-To: <87seszkldc.fsf@cbaines.net> (Christopher Baines's message of "Mon, 14 Oct 2024 11:51:59 +0100")
Hello,
Christopher Baines <mail@cbaines.net> skribis:
> The builds have been progressing. Substitute availability isn't quite as
> high as master yet, and there are probably some flaky builds that'll
> require more attempts to get substitutes, but it looks like this can be
> merged this week.
Yay, good.
> I had a look at why x86_64-linux on ci.guix.gnu.org is a bit behind, and
> some builds seem to be in the failed dependency state, but with no
> failed dependency listed. Clicking the restart button does prompt that
> thing to be built, but doesn't seem to unblock the builds on mass.
Right, I broke that with recent changes to Cuirass (I even wrote tests
that happen to not test the right thing…).
> 宋文武, are you available to push this once it's ready?
If not, we can probably do it on their behalf, in an effort to move
forward.
Thanks,
Ludo’.
next prev parent reply other threads:[~2024-10-15 15:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-02 10:27 [bug#72959] Request for merging "fonts-split-outputs" branch 宋文武 via Guix-patches via
2024-09-18 9:13 ` [bug#72959] Problem with data service? Andreas Enge
2024-09-18 9:21 ` Christopher Baines
2024-09-18 9:50 ` Andreas Enge
2024-09-18 10:25 ` Christopher Baines
2024-10-02 17:07 ` [bug#72959] Request for merging "fonts-split-outputs" branch Ludovic Courtès
2024-10-07 12:32 ` Ludovic Courtès
2024-10-10 17:52 ` Christopher Baines
2024-10-14 10:51 ` Christopher Baines
2024-10-15 15:40 ` Ludovic Courtès [this message]
2024-10-14 11:48 ` 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=875xptxtm6.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=72959@debbugs.gnu.org \
--cc=andreas@enge.fr \
--cc=iyzsong@envs.net \
--cc=mail@cbaines.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.
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).