all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Zheng Junjie <zhengjunjie@iscas.ac.cn>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Steve George <steve@futurile.net>, 73515-done@debbugs.gnu.org
Subject: bug#73515: Request for merging "qt-team" branch
Date: Thu, 21 Nov 2024 23:40:18 +0800	[thread overview]
Message-ID: <87wmgw61el.fsf@iscas.ac.cn> (raw)
In-Reply-To: <87ed34sleu.fsf_-_@gnu.org> ("Ludovic Courtès"'s message of "Thu, 21 Nov 2024 15:37:13 +0100")

[-- Attachment #1: Type: text/plain, Size: 774 bytes --]

Ludovic Courtès <ludo@gnu.org> writes:

> Hi,
>
> Z572 <zhengjunjie@iscas.ac.cn> skribis:
>
>> The other day I rebase to the latest commit, but qa doesn't seem to have
>> handled Merge base yet. and ci.guix's qt-team seems to work very slowly,
>> the submitted package will take a long time to start.
>
> <https://ci.guix.gnu.org/jobset/qt-team> is at 75% across all
> architectures; for reference, ‘master’ is at 78% (meaning that x86 is
> above 90% and aarch64 is very low).
>
> I would say it’s enough to make an informed decision as to whether to
> merge.

Yes, the other day I was waiting for bordeaux to build qt-team's aarch64 architecture.

Now I have pushed qt-team to master

Closed this issue.

>
> WDYT?
>
> Thanks,
> Ludo’.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

      reply	other threads:[~2024-11-21 15:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-27 12:43 [bug#73515] Request for merging "qt-team" branch Z572
2024-11-11 18:01 ` [bug#73515] Ready to merge qt-team branch? Steve George
2024-11-11 20:33   ` Christopher Baines
2024-11-11 21:07     ` Steve George
2024-11-12  5:28   ` Z572
2024-11-21 14:37     ` [bug#73515] Request for merging "qt-team" branch Ludovic Courtès
2024-11-21 15:40       ` Zheng Junjie [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=87wmgw61el.fsf@iscas.ac.cn \
    --to=zhengjunjie@iscas.ac.cn \
    --cc=73515-done@debbugs.gnu.org \
    --cc=ludo@gnu.org \
    --cc=steve@futurile.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 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.