From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Josselin Poiret <dev@jpoiret.xyz>
Cc: 61967@debbugs.gnu.org, cayetano.santos@inventati.org
Subject: bug#61967: guix pack error with python packages
Date: Thu, 09 Mar 2023 22:43:58 -0500 [thread overview]
Message-ID: <878rg5tgn5.fsf@gmail.com> (raw)
In-Reply-To: <87fsadd7ev.fsf@jpoiret.xyz> (Josselin Poiret's message of "Thu, 09 Mar 2023 20:57:44 +0100")
Hi Josselin,
Josselin Poiret <dev@jpoiret.xyz> writes:
> Hi Maxim,
>
> Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:
>
>> If you send it *after* the core-updates merge (to core-updates)? It's
>> going to be quite a while before it lands to master. Perhaps you could
>> send it now? core-updates is the right branch for mass rebuilds.
>
> I think we are trying to move away from the massive core-updates branch
> and rather work with feature branches instead, although the pending
> core-updates merge is blocking the change for now. I don't want to add
> yet more work for people courageously working on core-updates right now.
Perhaps I'm out of the loop, but in my book the main branches should
never close. If there's a need to freeze the state of one the three
main branches new development branches can be created. This was
discussed in the past.
--
Thanks,
Maxim
next prev parent reply other threads:[~2023-03-10 3:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-04 19:35 bug#61967: guix pack error with python packages Cayetano Santos via Bug reports for GNU Guix
2023-03-05 10:11 ` Josselin Poiret via Bug reports for GNU Guix
2023-03-07 21:08 ` Maxim Cournoyer
2023-03-09 19:57 ` Josselin Poiret via Bug reports for GNU Guix
2023-03-10 3:43 ` Maxim Cournoyer [this message]
2023-03-10 8:10 ` Josselin Poiret via Bug reports for GNU Guix
2023-06-05 19:53 ` bug#61967: (no subject) Cayetano Santos
2023-08-14 8:59 ` bug#61967: Fixed Cayetano Santos via Bug reports for GNU Guix
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=878rg5tgn5.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=61967@debbugs.gnu.org \
--cc=cayetano.santos@inventati.org \
--cc=dev@jpoiret.xyz \
/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).