From: Ross Burton <ross.burton@arm.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 2/3] classes/sbom-cve-check: remove references to vex.bbclass
Date: Tue, 31 Mar 2026 14:24:28 +0100 [thread overview]
Message-ID: <20260331132430.781647-2-ross.burton@arm.com> (raw)
In-Reply-To: <20260331132430.781647-1-ross.burton@arm.com>
This class has been deleted now, so remove the references to it and the
file that it writes.
This is effectively a no-op change, as the recommended way to run
sbom-cve-check is with SPDX_INCLUDE_VEX="all", which includes all of the
data in the SPDX that the vex class would have generated.
Signed-off-by: Ross Burton <ross.burton@arm.com>
---
meta/classes-recipe/sbom-cve-check.bbclass | 7 -------
1 file changed, 7 deletions(-)
diff --git a/meta/classes-recipe/sbom-cve-check.bbclass b/meta/classes-recipe/sbom-cve-check.bbclass
index a5dc262c6aa..2a8429d0b1c 100644
--- a/meta/classes-recipe/sbom-cve-check.bbclass
+++ b/meta/classes-recipe/sbom-cve-check.bbclass
@@ -48,7 +48,6 @@ python do_sbom_cve_check() {
bb.fatal("Cannot execute sbom-cve-check missing create-spdx-3.0 inherit.")
sbom_path = d.expand("${DEPLOY_DIR_IMAGE}/${IMAGE_LINK_NAME}.spdx.json")
- vex_manifest_path = d.expand("${DEPLOY_DIR_IMAGE}/${IMAGE_LINK_NAME}.vex.json")
dl_db_dir = d.getVar("SBOM_CVE_CHECK_DEPLOY_DB_DIR")
deploy_dir = d.getVar("SBOM_CVE_CHECK_DEPLOYDIR")
img_link_name = d.getVar("IMAGE_LINK_NAME")
@@ -72,12 +71,6 @@ python do_sbom_cve_check() {
"--disable-auto-updates"
]
- # Assume that SPDX_INCLUDE_VEX is set globally to "all", and not only for the
- # image recipe, which is very unlikely. This is not an issue to include the
- # VEX manifest even if not needed.
- if bb.data.inherits_class("vex", d) and d.getVar("SPDX_INCLUDE_VEX") != "all":
- cmd_args.extend(["--yocto-vex-manifest", vex_manifest_path])
-
for export_file in export_files:
cmd_args.extend(
["--export-type", export_file[0], "--export-path", export_file[1]]
--
2.43.0
next prev parent reply other threads:[~2026-03-31 13:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-31 13:24 [PATCH 1/3] classes/vex: remove Ross Burton
2026-03-31 13:24 ` Ross Burton [this message]
2026-03-31 13:24 ` [PATCH 3/3] classes/cve-check: remove class Ross Burton
2026-03-31 13:48 ` [OE-core] " Marko, Peter
2026-03-31 14:43 ` [OE-core] [PATCH 1/3] classes/vex: remove Marta Rybczynska
2026-03-31 15:04 ` Ross Burton
2026-03-31 15:13 ` Marta Rybczynska
2026-03-31 15:19 ` Ross Burton
2026-04-01 12:29 ` Daniel Turull
2026-04-02 14:42 ` Ross Burton
2026-04-02 14:53 ` Benjamin Robin
2026-04-07 7:39 ` Daniel Turull
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=20260331132430.781647-2-ross.burton@arm.com \
--to=ross.burton@arm.com \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox