From: michael@moysys.com
To: buildroot@buildroot.org
Subject: [Buildroot] [2026.08.x] Incomplete python-pkg-resources backport breaks U-Boot binman builds
Date: Sun, 15 Nov 2026 17:51:05 -0500 [thread overview]
Message-ID: <4a65b600f69b00a8366293ab1df6a2bc@moysys.com> (raw)
Hi,
The nightly build of my 2026.08.x KV260 configuration has failed since
the stable batch of Oct 29. The build stops with:
make: *** No rule to make target 'host-python-jaraco-text', needed by
'.../build/host-python-pkg-resources-7fa76c17eacf8a67c6932c9c2dd97861f42439cf/.stamp_configured'.
Stop.
The cause seems to be these two commits, which were backported to
2026.08.x:
c58cbe478a package/python-pkg-resources: new host package
c647377c53 boot/uboot: add host-python-pkg-resources dependency
On master, these commits come after a series that adds host variants for
the packages they depend on (760fd221a1 "package/python-jaraco-text: add
host variant", along with jaraco-context, jaraco-functools,
more-itertools, typer-slim, typer and others). That series was not
backported. As a result, on 2026.08.x:
- python-jaraco-text has no host variant, but
HOST_PYTHON_PKG_RESOURCES_DEPENDENCIES requires host-python-jaraco-text
- host-python-jaraco-text would in turn need host variants of
jaraco-context, jaraco-functools, more-itertools and typer-slim, which
are also missing
Any configuration with BR2_TARGET_UBOOT_USE_BINMAN=y now fails to build,
because U-Boot pulls in host-python-pkg-resources.
I tried cherry-picking the host-variant series onto 2026.08.x, but it
conflicts (python-shellingham, for example, does not exist on the
branch).
As a workaround, I reverted c647377c53 and c58cbe478a locally, and my
build passes again with binman working. That is expected, since
2026.08.x still uses setuptools 80.9.0, which includes pkg_resources, so
the standalone package should not be needed on this branch.
The 2026.08.1 tag predates this backport and is not affected.
Thanks,
Michael Moy and Claude Code
michael@moysys.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2026-11-15 22:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-15 22:51 michael [this message]
2026-11-16 10:46 ` [Buildroot] [2026.08.x] Incomplete python-pkg-resources backport breaks U-Boot binman builds Thomas Perale 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=4a65b600f69b00a8366293ab1df6a2bc@moysys.com \
--to=michael@moysys.com \
--cc=buildroot@buildroot.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.
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.