From: Christopher Baines <mail@cbaines.net>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: 63521@debbugs.gnu.org
Subject: [bug#63521] Request for merging "tex-team" branch
Date: Tue, 16 May 2023 13:05:55 +0100 [thread overview]
Message-ID: <87mt24eapk.fsf@cbaines.net> (raw)
In-Reply-To: <87zg641o3b.fsf@nicolasgoaziou.fr>
[-- Attachment #1: Type: text/plain, Size: 1311 bytes --]
Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
> Christopher Baines <mail@cbaines.net> writes:
>
>> While I realise that waiting to make changes is fustrating, I think it's
>> important to try and build things before merging so that the effects are
>> known. This is also good motivation to get more hardware helping to
>> build things to speed up the process.
>
> I opened the issue because the "tex-team" branch was fully built on
> CI, according to <https://ci.guix.gnu.org/eval/461653>.
>
> Should I have looked elsewhere before asking for the merge?
I see opening the issue as something to do near the middle of the
process. Similar to opening an issue for some patches, so I think now is
a good time.
However, I'd be sceptical of what you see at [1]. I'm guessing what
you're seeing is correct (at least in the sense of Cuirrass), but there
being no more scheduled builds doesn't mean the branch is good to merge.
1: https://ci.guix.gnu.org/eval/461653
You can see here [2] that while substitute availability is OK for
x86_64-linux and i686-linux, it's poor for all other systems. Also, I
think this might not actually relate to changes on the branch,
substitute availability for aarch64-linux is poor from ci.guix.gnu.org
on the master branch as well.
2: https://qa.guix.gnu.org/branch/tex-team
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]
next prev parent reply other threads:[~2023-05-16 12:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 15:48 [bug#63521] Request for merging "tex-team" branch Nicolas Goaziou
2023-05-16 9:57 ` Christopher Baines
2023-05-16 12:02 ` Nicolas Goaziou
2023-05-16 12:05 ` Christopher Baines [this message]
2023-05-22 14:06 ` Ludovic Courtès
2023-05-22 14:36 ` Christopher Baines
2023-05-23 13:20 ` Christopher Baines
2023-05-24 14:36 ` Ludovic Courtès
2023-05-24 14:37 ` Ludovic Courtès
2023-05-24 17:28 ` Nicolas Goaziou
2023-05-25 9:13 ` Christopher Baines
2023-06-02 9:46 ` Christopher Baines
2023-06-02 20:08 ` Nicolas Goaziou
2023-06-11 9:31 ` Christopher Baines
2023-06-11 16:18 ` bug#63521: " Nicolas Goaziou
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=87mt24eapk.fsf@cbaines.net \
--to=mail@cbaines.net \
--cc=63521@debbugs.gnu.org \
--cc=mail@nicolasgoaziou.fr \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
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.