From: Steve George <steve@futurile.net>
To: jgart <jgart@dismail.de>,
Sharlatan Hellseher <sharlatanus@gmail.com>,
Christopher Baines <mail@cbaines.net>
Cc: Ricardo Wurmus <rekado@elephly.net>,
Lars-Dominik Braun <lars@6xq.net>,
guix-devel <guix-devel@gnu.org>,
Nicolas Graves <ngraves@ngraves.fr>,
Felix Gruber <felgru@posteo.net>
Subject: Re: Status of python-team branch
Date: Thu, 26 Sep 2024 23:15:24 +0100 [thread overview]
Message-ID: <2ca00550-a818-4aa9-a36a-c16b7b6562cf@futurile.net> (raw)
In-Reply-To: <009929435a373a0b7600f6a0304bdadb8097b5bb@dismail.de>
Hi,
I got 31 from the 'start' of the branch applied:
https://issues.guix.gnu.org/71408#13
There are notes on the ones I couldn't get working, and the
python-project build system ones that Lars was going to cherry-pick
separately.
I've rebuild about 100+ dependent packages. But some of these require 2k
dependent packages to be rebuilt! From what I can tell these 31 don't
make master 'worse' (insufficient sample etc).
I'll create a second branch and 'stack' it on top of this first one, and
keep going. There are 231 commits in total, so 10% at a time!
Steve / Futurile
On 26/09/2024 18:27, jgart wrote:
>
> Same for me, starting resolving rebase conflict.
>
>
> Hi Guixers,
>
> I would recommend cherry picking logical commits into new branches that
> can be quickly reviewed and merged by Guix volunteers.
>
> Steve made a list here of some logical commits that can go into new
> branches:
>
> https://issues.guix.gnu.org/71408#11 <https://issues.guix.gnu.org/71408#11>
>
> Feel free to send small patch sets of those for review by Guix
> volunteers to look at.
>
> I can take some time to review and apply such small patches and test them.
>
> all the best,
>
> jgart
>
next prev parent reply other threads:[~2024-09-26 22:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-12 10:27 Status of python-team branch Sharlatan Hellseher
2024-08-12 16:24 ` Lars-Dominik Braun
2024-08-12 19:42 ` Ricardo Wurmus
2024-09-02 16:00 ` Ricardo Wurmus
2024-09-02 17:45 ` Sharlatan Hellseher
2024-09-02 20:16 ` jgart
2024-09-26 15:01 ` Christopher Baines
2024-09-26 16:14 ` Sharlatan Hellseher
2024-09-26 17:27 ` jgart
2024-09-26 22:15 ` Steve George [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-09-24 11:03 Sharlatan Hellseher
2024-09-24 13:28 ` Arseniy Zaostrovnykh
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=2ca00550-a818-4aa9-a36a-c16b7b6562cf@futurile.net \
--to=steve@futurile.net \
--cc=felgru@posteo.net \
--cc=guix-devel@gnu.org \
--cc=jgart@dismail.de \
--cc=lars@6xq.net \
--cc=mail@cbaines.net \
--cc=ngraves@ngraves.fr \
--cc=rekado@elephly.net \
--cc=sharlatanus@gmail.com \
/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).