From: Stefano Tondo <stondo@gmail.com>
To: openembedded-core@lists.openembedded.org
Cc: jpewhacker@gmail.com, peter.marko@siemens.com,
adrian.freihofer@siemens.com, Stefano Tondo <stondo@gmail.com>
Subject: [PATCH 0/3] spdx30: Fix two bugs in the source download enrichment
Date: Wed, 4 Nov 2026 12:22:54 +0100 [thread overview]
Message-ID: <20261104112257.866914-1-stondo@gmail.com> (raw)
Two fixes for the source download enrichment added in 9f1825e74d
("spdx30: Add Git version and PURL to source downloads"):
- _enrich_source_package() and _generate_git_purl() start with an
underscore, so bitbake leaves them out of the do_create_spdx
signature, and SPDX_GIT_PURL_MAPPINGS with them. Changing the
mappings restored the previous SPDX from sstate.
- gitsm downloads got no version and no PURL, because only fd.type
"git" was handled.
Patch 1 changes the do_create_spdx signature of every recipe once.
Patch 3 adds one selftest per fix. Each fails on master without its
fix. With the series, all SPDX30Check selftests pass.
Stefano Tondo (3):
spdx30: Make source download enrichment part of the task signature
spdx30: Enrich gitsm source downloads like git ones
oeqa/selftest: Add tests for source download enrichment
meta/lib/oe/spdx30_tasks.py | 10 +++---
meta/lib/oeqa/selftest/cases/spdx.py | 47 ++++++++++++++++++++++++++++
2 files changed, 52 insertions(+), 5 deletions(-)
--
2.56.0
next reply other threads:[~2026-11-04 11:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 11:22 Stefano Tondo [this message]
2026-11-04 11:22 ` [PATCH 1/3] spdx30: Make source download enrichment part of the task signature Stefano Tondo
2026-11-04 11:22 ` [PATCH 2/3] spdx30: Enrich gitsm source downloads like git ones Stefano Tondo
2026-11-04 11:22 ` [PATCH 3/3] oeqa/selftest: Add tests for source download enrichment 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=20261104112257.866914-1-stondo@gmail.com \
--to=stondo@gmail.com \
--cc=adrian.freihofer@siemens.com \
--cc=jpewhacker@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=peter.marko@siemens.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.