From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: buildroot@uclibc.org
Subject: Re: [Buildroot] [PATCH 2/2] package/python3: bump version to 3.15.2
Date: Thu, 29 Oct 2026 22:49:11 +0100 [thread overview]
Message-ID: <auO--UQbUihysaGa@windsurf> (raw)
In-Reply-To: <pan$ae294$bd983f48$791067ea$427f8b9c@ID-313208.user.individual.net>
On Thu, Oct 29, 2026 at 10:33:19PM +0100, Bernd Kuhls wrote:
> yes, I mentioned the new series in the work item:
> https://gitlab.com/buildroot.org/buildroot/-/work_items/
> 193#note_4120357815
>
> so he can use the newest python version for testing.
>
> My personal repo does not contain any python-related bumps anymore so I
> will try to help Vincent in the coming days.
OK, but what bothers me is that your submission is presented as if it
is ready to be merged while in fact it isn't as this bump breaks a lot
of Python packages. I am fine with work-in-progress patches being
submitted, but they should clearly be marked as such, and the
remaining work to be done made clear in the patch description.
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-10-29 21:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-29 20:49 [Buildroot] [PATCH 1/2] package/ncurses: install wide-char headers in usr/include/ncursesw/ Bernd Kuhls
2026-10-29 20:49 ` [Buildroot] [PATCH 2/2] package/python3: bump version to 3.15.2 Bernd Kuhls
2026-10-29 21:13 ` Thomas Petazzoni via buildroot
[not found] ` <auO2ugenOrGrEKGM__30665.5666836136$1793308450$gmane$org@windsurf>
2026-10-29 21:33 ` Bernd Kuhls
2026-10-29 21:49 ` Thomas Petazzoni via buildroot [this message]
2026-10-29 21:12 ` [Buildroot] [PATCH 1/2] package/ncurses: install wide-char headers in usr/include/ncursesw/ Thomas Petazzoni via buildroot
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=auO--UQbUihysaGa@windsurf \
--to=buildroot@buildroot.org \
--cc=bernd@kuhls.net \
--cc=buildroot@uclibc.org \
--cc=thomas.petazzoni@bootlin.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.