From: Stefano Tondo <stondo@gmail.com>
To: bitbake-devel@lists.openembedded.org
Cc: Thomas Perrot <thomas.perrot@bootlin.com>,
Alexander Kanavin <alex.kanavin@gmail.com>,
Stefan Herbrechtsmeier <stefan.herbrechtsmeier@weidmueller.com>,
Peter Marko <peter.marko@siemens.com>,
stefano.tondo.ext@siemens.com
Subject: [PATCH 0/2] fetch/npm: no npm executable, and an event log fix
Date: Fri, 20 Nov 2026 14:53:21 +0100 [thread overview]
Message-ID: <20261120135323.2627478-1-stondo@gmail.com> (raw)
Hi,
The OE-Core series "npm: list the dependencies in SRC_URI" needs these
two patches. I send that series at the same time. The two patches do
not depend on each other.
1. cooker: "recipetool create" for npm runs two builds in one server.
The second build fails to write the event log, because
sstate.bbclass stores compiled regular expressions in the
datastore. The recipetool selftest of the OE-Core series shows this
failure.
2. fetch/npm: Alexander asked for this in the RFC thread [1]. The npm
fetcher must work without the npm executable, as the crate fetcher
works without cargo. The npm tests now run without npm, and new
tests fetch a package from a premirror without network access.
Tests: bitbake-selftest bb.tests.fetch.NPMTest passes, with an npm in
PATH that always fails. bb.tests.event and bb.tests.cooker pass.
[1] https://lore.kernel.org/openembedded-core/20261111115845.1940227-1-stondo@gmail.com/T/
Stefano Tondo (2):
cooker: Write variables that are not JSON types to the event log
fetch/npm: Build the tarball URL without the npm executable
lib/bb/cooker.py | 2 +-
lib/bb/fetch/npm.py | 50 +++----------------------
lib/bb/tests/fetch.py | 85 ++++++++++++++++++++++---------------------
3 files changed, 50 insertions(+), 87 deletions(-)
--
2.56.1
next reply other threads:[~2026-11-20 13:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-20 13:53 Stefano Tondo [this message]
2026-11-20 13:53 ` [PATCH 1/2] cooker: Write variables that are not JSON types to the event log Stefano Tondo
2026-11-20 18:46 ` [bitbake-devel] " Richard Purdie
2026-11-20 13:53 ` [PATCH 2/2] fetch/npm: Build the tarball URL without the npm executable Stefano Tondo
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=20261120135323.2627478-1-stondo@gmail.com \
--to=stondo@gmail.com \
--cc=alex.kanavin@gmail.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=peter.marko@siemens.com \
--cc=stefan.herbrechtsmeier@weidmueller.com \
--cc=stefano.tondo.ext@siemens.com \
--cc=thomas.perrot@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.