From: Ricardo Wurmus <rekado@elephly.net>
To: Lars-Dominik Braun <lars@6xq.net>
Cc: Tanguy Le Carrour <tanguy@bioneland.org>,
Munyoki Kilyungi <me@bonfacemunyoki.com>,
75246@debbugs.gnu.org, jgart <jgart@dismail.de>,
Marius Bakke <marius@gnu.org>,
Sharlatan Hellseher <sharlatanus@gmail.com>
Subject: [bug#75246] Request for merging "python-team" branch
Date: Sun, 05 Jan 2025 13:22:47 +0100 [thread overview]
Message-ID: <87a5c55u20.fsf@elephly.net> (raw)
In-Reply-To: <Z3pgSd60hE8LN1uE@noor.fritz.box> (Lars-Dominik Braun's message of "Sun, 5 Jan 2025 11:34:49 +0100")
Hi Lars,
>> The python-team branch is currently tracking the rust-team branch,
>> because it depends on changes there. It is shaping up nicely and we
>> hope to be able to merge it some time soon.
>
> I recall you wanted to keep python-team small, but do you mind if I
> push https://issues.guix.gnu.org/74993 there (it’s a small, but
> world-rebuilding change)?
Looks fine to me. Would this fix the build failure we see in
python-fastapi-pagination-minimal, which seems to be due to a parse
error?
I know I said I wanted to merge this branch quickly and keep the changes
restricted to important fixes, but it turned out that many of the
required fixes are wide-ranging anyway. I had to upgrade a lot of
packages that led to thousands of rebuilds. At this point I'd still
like to keep *experimental* changes out, but almost all other
improvements are welcome.
Thank you!
--
Ricardo
next prev parent reply other threads:[~2025-01-05 12:24 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-01 17:58 [bug#75246] Request for merging "python-team" branch Ricardo Wurmus
2025-01-05 10:34 ` Lars-Dominik Braun
2025-01-05 12:22 ` Ricardo Wurmus [this message]
2025-01-05 13:00 ` Lars-Dominik Braun
2025-01-05 13:02 ` Ricardo Wurmus
2025-01-05 20:18 ` jgart via Guix-patches via
2025-01-13 13:10 ` [bug#75246] Last minute python-team fixes: help needed! Ricardo Wurmus
2025-01-14 20:47 ` [bug#75246] Request for merging "python-team" branch Sharlatan Hellseher
2025-01-16 8:44 ` Ricardo Wurmus
2025-01-16 9:51 ` Ricardo Wurmus
2025-01-16 10:18 ` Sharlatan Hellseher
2025-01-16 21:22 ` Ricardo Wurmus
2025-01-16 21:33 ` Ricardo Wurmus
2025-01-17 19:57 ` Leo Famulari
2025-01-17 20:42 ` jgart via Guix-patches via
2025-01-17 23:33 ` Leo Famulari
2025-01-18 0:15 ` jgart via Guix-patches via
2025-01-18 4:24 ` Christopher Baines
2025-01-19 13:07 ` Ricardo Wurmus
2025-01-20 20:56 ` Ricardo Wurmus
2025-01-20 22:46 ` bug#75246: " Leo Famulari
2025-01-20 21:19 ` [bug#75246] " Sharlatan Hellseher
2025-01-21 10:32 ` Ricardo Wurmus
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=87a5c55u20.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=75246@debbugs.gnu.org \
--cc=jgart@dismail.de \
--cc=lars@6xq.net \
--cc=marius@gnu.org \
--cc=me@bonfacemunyoki.com \
--cc=sharlatanus@gmail.com \
--cc=tanguy@bioneland.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).