From: "Paul Barker" <paul@pbarker.dev>
To: "Stefano Tondo" <stondo@gmail.com>,
<openembedded-core@lists.openembedded.org>
Cc: "Joshua Watt" <JPEWhacker@gmail.com>,
"Alexander Kanavin" <alex.kanavin@gmail.com>,
"Stefan Herbrechtsmeier" <stefan.herbrechtsmeier@weidmueller.com>,
"Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>,
<stefano.tondo.ext@siemens.com>
Subject: Re: [PATCH v2 4/4] oeqa/selftest: spdx: Test crate identity, scope and output PURLs
Date: Thu, 19 Nov 2026 10:03:02 +0000 [thread overview]
Message-ID: <DMZ3O22TVVFQ.155PGZ293VQJO@pbarker.dev> (raw)
In-Reply-To: <20261118234425.3681880-5-stondo@gmail.com>
On Wed Nov 18, 2026 at 11:44 PM GMT, Stefano Tondo wrote:
> From: Stefano Tondo <stefano.tondo.ext@siemens.com>
>
> python3-bcrypt fetches 42 crates. The new tests check three things:
>
> - Each crate download has its name, version and PURL.
> - Each crate download has a lifecycle scope, or an annotation that it
> is not built.
> - The output package gets the PURLs of the runtime crates only.
>
> The tests name only crates that do not change on recipe upgrades.
> blowfish is the cipher of bcrypt. Only the pyo3 proc-macros use syn,
> at build time. The other checks do not use crate names.
Hi Stefano,
A couple of quick questions about this test case.
Does it use a fixed version of the python3-bcrypt recipe or just
whatever version is currently in OE-Core?
If it tracks the version used in OE-Core, is it likely to start failing
when python3-bcrypt adds or removes dependencies in the future?
Best regards,
--
Paul Barker
next prev parent reply other threads:[~2026-11-19 10:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-18 23:44 [PATCH v2 0/4] spdx30: identity and purls of dependency downloads Stefano Tondo
2026-11-18 23:44 ` [PATCH v2 1/4] spdx30: Take name, version and PURL of downloads from the fetcher Stefano Tondo
2026-11-18 23:44 ` [PATCH v2 2/4] spdx30: Record the lifecycle scope of crate dependencies Stefano Tondo
2026-11-18 23:44 ` [PATCH v2 3/4] spdx30: Add the PURLs of the source downloads to the output packages Stefano Tondo
2026-11-18 23:44 ` [PATCH v2 4/4] oeqa/selftest: spdx: Test crate identity, scope and output PURLs Stefano Tondo
2026-11-19 10:03 ` Paul Barker [this message]
2026-11-19 10:30 ` Stefano Tondo
2026-11-19 12:34 ` [PATCH v2 0/4] spdx30: identity and purls of dependency downloads Mathieu Dubois-Briand
2026-11-19 13:35 ` Stefano Tondo
2026-11-19 16:37 ` Mathieu Dubois-Briand
[not found] ` <18E97F9E4135A022.1484727@lists.openembedded.org>
2026-11-19 16:43 ` [OE-core] " Mathieu Dubois-Briand
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=DMZ3O22TVVFQ.155PGZ293VQJO@pbarker.dev \
--to=paul@pbarker.dev \
--cc=JPEWhacker@gmail.com \
--cc=alex.kanavin@gmail.com \
--cc=mathieu.dubois-briand@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=stefan.herbrechtsmeier@weidmueller.com \
--cc=stefano.tondo.ext@siemens.com \
--cc=stondo@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 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.