From: Peter Korsgaard <peter@korsgaard.com>
To: James Hilliard <james.hilliard1@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] Revert "package/python-setuptools: bump to version 82.0.0"
Date: Sat, 09 May 2026 22:49:36 +0200 [thread overview]
Message-ID: <87pl34pau7.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CADvTj4p1VpLavsumv0zp4dZic7ejyooSXGthS_=qqgP6=yd1Tg@mail.gmail.com> (James Hilliard's message of "Sat, 9 May 2026 13:00:42 -0600")
>>>>> "James" == James Hilliard <james.hilliard1@gmail.com> writes:
> On Sat, May 9, 2026 at 3:38 AM Peter Korsgaard <peter@korsgaard.com> wrote:
>>
>> This reverts commit 51365ff06379aaf6fcc9a751e8ff32ac694f3e92.
>>
>> This breaks u-boot < v2025.10 builds using binman, so revert it for now
>> given that v2025.10 is a quite recent release.
>>
>> Fixes: https://gitlab.com/buildroot.org/buildroot/-/jobs/14249332016
>> And many more.
>>
>> Longer term we either want to upgrade all the defconfigs (which will not fix
>> the issue for external users) or find a way to patch older u-boot versions.
> Maybe we can install this somehow for compatibility?:
> https://github.com/pypa/pkg_resources
Yes, that may be a solution longer term. I would like to tag -rc1 very
soon, so I still think that a revert is maybe the best for 2026.05.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-05-09 20:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-09 9:38 [Buildroot] [PATCH] Revert "package/python-setuptools: bump to version 82.0.0" Peter Korsgaard
2026-05-09 19:00 ` James Hilliard
2026-05-09 20:49 ` Peter Korsgaard [this message]
2026-05-11 10:20 ` Peter Korsgaard
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=87pl34pau7.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=james.hilliard1@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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox