Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fiona Klute <fiona.klute@gmx.de>
Cc: buildroot@buildroot.org,
	James Hilliard <james.hilliard1@gmail.com>,
	 Bernd Kuhls <bernd@kuhls.net>
Subject: Re: [Buildroot] [PATCH 1/1] package/python-charset-normalizer: skip dependency check
Date: Mon, 26 Oct 2026 11:59:21 +0100	[thread overview]
Message-ID: <at8yg8Kr3FPGv-t3@windsurf> (raw)
In-Reply-To: <20261025212732.4111719-1-fiona.klute@gmx.de>

On Sun, Oct 25, 2026 at 10:27:32PM +0100, Fiona Klute via buildroot wrote:
> Upstream has set an upper bound for the setuptools version [1],
> banning >=84.1, which had not even been released yet at the time
> (setuptools 84.1.0 was released 2026-10-19). Because of this the build
> fails since Buildroot commit 2027954db7f5f42ed976ea2f4655e0cd224c7ee7
> ("package/python-setuptools: bump to version 84.2.1"). Nonetheless the
> package actually builds fine with python-setuptools 84.2.1, so disable
> the dependency check.
> 
> [1] https://github.com/jawah/charset_normalizer/commit/a05917f87b5f71d6022d8abe2b0af239f65c1111
> 
> Signed-off-by: Fiona Klute <fiona.klute@gmx.de>

Applied to master, thanks!

Best regards,

Thomas Petazzoni
-- 
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

      reply	other threads:[~2026-10-26 10:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-25 21:27 [Buildroot] [PATCH 1/1] package/python-charset-normalizer: skip dependency check Fiona Klute via buildroot
2026-10-26 10:59 ` Thomas Petazzoni via buildroot [this message]

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=at8yg8Kr3FPGv-t3@windsurf \
    --to=buildroot@buildroot.org \
    --cc=bernd@kuhls.net \
    --cc=fiona.klute@gmx.de \
    --cc=james.hilliard1@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox