From: Christopher Baines <mail@cbaines.net>
To: Christopher Baines <mail@cbaines.net>
Cc: 63521@debbugs.gnu.org, Nicolas Goaziou <mail@nicolasgoaziou.fr>
Subject: [bug#63521] Request for merging "tex-team" branch
Date: Fri, 02 Jun 2023 10:46:38 +0100 [thread overview]
Message-ID: <875y866vjq.fsf@cbaines.net> (raw)
In-Reply-To: <87jzww4vmf.fsf@cbaines.net>
[-- Attachment #1: Type: text/plain, Size: 1790 bytes --]
Christopher Baines <mail@cbaines.net> writes:
> [[PGP Signed Part:Good signature from 5E28A33B0B84F577 Christopher Baines <mail@cbaines.net> (trust ultimate) created at 2023-05-25T10:18:32+0100 using RSA]]
>
> Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
>
>> Ludovic Courtès <ludo@gnu.org> writes:
>>
>>> Christopher Baines <mail@cbaines.net> skribis:
>>
>>>> Maybe the branch could be rebased or master could be merged in? If you
>>>> pick the latest commit with a green tick by it from [1], then that
>>>> should mean the data service is able to perform the comparison.
>>>
>>> Sounds like a plan. Nicolas?
>>
>> I rebased the branch on top of c57693846c7c6586c6cd1b4e4002fe399e3a2c42,
>> which is as green-ticked as a commit can be.
>
> Awesome, the comparison is available now. I've also got the qa-frontpage
> to find this issue and start submitting builds (this time for most
> systems, not just x86_64-linux).
>
> The QA link at the top (of https://issues.guix.gnu.org/63521 ) should
> now also take you to the relevant page.
>
> There's now some waiting to do for the builds to happen, but also more
> work needed on the qa-frontpage to better show any breakages and
> failures that occur.
So I still need to do this, however the more significant problem is that
master has diverged significantly (in part at least due to the eudev
change [1] not going to core-updates/another branch).
1: https://lists.gnu.org/archive/html/guix-devel/2023-05/msg00330.html
I've got the qa-frontpage to flag this now, so there should be a warning
at the top of [2] saying there's too many changes between the merge base
and master.
2: https://qa.guix.gnu.org/branch/tex-team
Would you be able to rebase the branch again?
Thanks,
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]
next prev parent reply other threads:[~2023-06-02 9:53 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
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 [this message]
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
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=875y866vjq.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 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).