GNU bug report logs - #75751
Request for merging "python-team" branch

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Andreas Enge <andreas <at> enge.fr>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#75751: closed (Request for merging "python-team" branch)
Date: Mon, 07 Apr 2025 08:12:01 +0000

[Message part 1 (text/plain, inline)]

Your message dated Mon, 7 Apr 2025 10:10:53 +0200
with message-id <Z_OIjazviGUp9KQB <at> jurong>
and subject line Re: [bug#75751] Request for merging "python-team" branch
has caused the debbugs.gnu.org bug report #75751,
regarding Request for merging "python-team" branch
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
75751: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=75751
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Ricardo Wurmus <rekado <at> elephly.net>
To: guix-patches <at> gnu.org
Subject: Request for merging "python-team" branch
Date: Wed, 22 Jan 2025 10:09:28 +0100

Hi Guix,

This marks the beginning of work on the next iteration of the
python-team branch.

Goals:

- add Python 3.11 and make it the default
- update python-numpy and co to the latest 1.x release.

Let's try to keep this a *short* iteration.  I'd love to merge this
within a month, i.e. before the end of February 2025.

-- 
Ricardo

[Message part 3 (message/rfc822, inline)]

From: Andreas Enge <andreas <at> enge.fr>
To: Nicolas Graves <ngraves <at> ngraves.fr>
Cc: Ricardo Wurmus <rekado <at> elephly.net>, Christopher Baines <mail <at> cbaines.net>,
 Sharlatan Hellseher <sharlatanus <at> gmail.com>, 75751-done <at> debbugs.gnu.org
Subject: Re: [bug#75751] Request for merging "python-team" branch
Date: Mon, 7 Apr 2025 10:10:53 +0200

Hello all,

from the discussion I deduce that you will still need a week or two
until the branch can be merged. So I am closing it momentarily, so that
the node branch gets a chance of being built on QA.

This does not prevent discussions from continuing on this bug.

Once you think you are ready, just rebase the python-team branch on a
recent commit known to the data service - I think it is one of the
commits shown in green at
   https://data.qa.guix.gnu.org/repository/1/branch/master

If you then reopen the bug, the python-team branch should jump back to
its place at the front of the queue and be built again.

Chris, I wonder if we could add some way of interacting more directly on
QA than by closing and opening bugs? In this case, we could add a third
branch to the number of evaluations (which we might want to lower to 2
again once the python-team branch is back). But this would probably mean
reconfiguring one of the machines?

Andreas

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.