unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: 71408@debbugs.gnu.org
Subject: [bug#71408] Postpone?
Date: Wed, 18 Sep 2024 11:09:23 +0200	[thread overview]
Message-ID: <ZuqYw8w-aC3eCTz6@jurong> (raw)
In-Reply-To: <8734pp2m98.fsf@cbaines.net>

This branch is first now on the waiting list of QA:
   https://qa.guix.gnu.org/
but it has not been touched since May, and in particular not been
rebased on master after the core-updates merge. This is reflected
in the QA message:
   https://qa.guix.gnu.org/branch/python-team
   "Unable to check changes between branch and master.
   Merge base is not a commit known to the data service."

Should we close this issue now and let the branch take the back of the
queue? I see build farm activity around commit e4ad2f178af65be6c8ca6e98a667787674cd8c82,
the latest one in this branch, which looks like a waste of scarce build
power (especially on aarch64) to me. And it holds up the r-team branch
described as ready to merge.

Andreas





  parent reply	other threads:[~2024-09-18  9:11 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-07  8:24 [bug#71408] Request for merging "python-team" branch Christopher Baines
2024-06-08 14:27 ` Ludovic Courtès
2024-06-08 21:04   ` Sharlatan Hellseher
2024-06-18 20:46 ` jgart via Guix-patches via
2024-06-19  7:28   ` Tanguy LE CARROUR
2024-06-19 13:45   ` Christopher Baines
2024-06-25 17:04     ` jgart via Guix-patches via
2024-06-25 18:06       ` Sharlatan Hellseher via Guix-patches
2024-09-24  7:25         ` Steve George
2024-06-30  7:31       ` Lars-Dominik Braun
2024-06-30  9:42       ` Christopher Baines
2024-09-18  9:09 ` Andreas Enge [this message]
2024-09-27  7:30   ` bug#71408: Postpone? Andreas Enge
2024-09-24 13:31 ` [bug#71408] Request for merging "python-team" branch Arseniy Zaostrovnykh
2024-09-26 21:54 ` [bug#71408] Update on Python team pt1 Steve George

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=ZuqYw8w-aC3eCTz6@jurong \
    --to=andreas@enge.fr \
    --cc=71408@debbugs.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).