sbom-cve-check: set PV from upstream tags and ensure version checks are correct
PATCH 1/1 sbom-cve-check: set PV from upstream tags and ensure version checks are correct
From: Alexander Kanavin <[email protected]>
These recipes didn't set PV, which by default is 1.0. This isn't correct:
upstream does provide date-based tags that can be used to perform version upgrades.
---
...ve.bb => sbom-cve-check-update-cvelist-native_2026-05-07.bb} | 2 +-
...bb => sbom-cve-check-update-nvd-native_2026.05.07-000006.bb} | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-devtools/sbom-cve-check/{sbom-cve-check-update-cvelist-native.bb => sbom-cve-check-update-cvelist-native_2026-05-07.bb} (88%)
rename meta/recipes-devtools/sbom-cve-check/{sbom-cve-check-update-nvd-native.bb => sbom-cve-check-update-nvd-native_2026.05.07-000006.bb} (90%)meta/recipes-devtools/sbom-cve-check/sbom-cve-check-update-cvelist-native_2026-05-07.bb renamed from meta/recipes-devtools/sbom-cve-check/sbom-cve-check-update-cvelist-native.bb +1 -1
@@ -6,7 +6,7 @@ HOMEPAGE = "https://github.com/CVEProject/cvelistV5" SRC_URI = "git://github.com/CVEProject/cvelistV5.git;branch=main;protocol=https;destsuffix=" SBOM_CVE_CHECK_DB_NAME = "cvelist" -# cve_2026-05-07_1300Z SRCREV = "dd0e93c75034d0167498174c886a56729edc44de" +UPSTREAM_CHECK_GITTAGREGEX = "(?P<pver>.+)_baseline" require sbom-cve-check-update-db.inc
meta/recipes-devtools/sbom-cve-check/sbom-cve-check-update-nvd-native_2026.05.07-000006.bb renamed from meta/recipes-devtools/sbom-cve-check/sbom-cve-check-update-nvd-native.bb +1 -1
@@ -6,7 +6,7 @@ HOMEPAGE = "https://github.com/fkie-cad/nvd-json-data-feeds" SRC_URI = "git://github.com/fkie-cad/nvd-json-data-feeds.git;branch=main;protocol=https;destsuffix=" SBOM_CVE_CHECK_DB_NAME = "nvd-fkie" -# v2026.05.07-000006 SRCREV = "72d8841c8ad9083ebf6723063f275444ea0d76f9" +UPSTREAM_CHECK_GITTAGREGEX = "v(?P<pver>.+)" require sbom-cve-check-update-db.inc
Signature · 1 line
2.47.3
Quoted 12 lines
-----Original Message-----
From: [email protected] <openembedded- [email protected]> On Behalf Of Alexander Kanavin via lists.openembedded.org
Sent: Tuesday, May 12, 2026 12:10 PM
To: [email protected]
Cc: Alexander Kanavin <[email protected]>
Subject: [OE-core] [PATCH] sbom-cve-check: set PV from upstream tags and ensure version checks are correct
Quoted 3 lines
From: Alexander Kanavin <[email protected]>
These recipes didn't set PV, which by default is 1.0. This isn't correct:
This is probably old commit message that claims PV being 1.0.
I can see version provided in filename of recipes being updated in this commit.
Quoted 62 lines
upstream does provide date-based tags that can be used to perform version upgrades.
Signed-off-by Alexander Kanavin <[email protected]>--- ...ve.bb => sbom-cve-check-update-cvelist-native_2026-05-07.bb} | 2 +- ...bb => sbom-cve-check-update-nvd-native_2026.05.07-000006.bb} | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) rename meta/recipes-devtools/sbom-cve-check/{sbom-cve-check-update-cvelist- native.bb => sbom-cve-check-update-cvelist-native_2026-05-07.bb} (88%) rename meta/recipes-devtools/sbom-cve-check/{sbom-cve-check-update-nvd-native.bb => sbom-cve-check-update-nvd-native_2026.05.07-000006.bb} (90%)
(quoted diff) +0
-0native.bb b/meta/recipes-devtools/sbom-cve-check/sbom-cve-check-update- cvelist-native_2026-05-07.bb
similarity index 88%
rename from meta/recipes-devtools/sbom-cve-check/sbom-cve-check-update- cvelist-native.bb
rename to meta/recipes-devtools/sbom-cve-check/sbom-cve-check-update- cvelist-native_2026-05-07.bb
index3763e7f21f..7670172c40100644
--- a/meta/recipes-devtools/sbom-cve-check/sbom-cve-check-update-cvelist- native.bb
+++ b/meta/recipes-devtools/sbom-cve-check/sbom-cve-check-update-cvelist- native_2026-05-07.bb(quoted diff) +0
-0@@ -6,7 +6,7 @@ HOMEPAGE = "https://github.com/CVEProject/cvelistV5" SRC_URI ="
git://github.com/CVEProject/cvelistV5.git;branch=main;protocol=https;destsuffix="
SBOM_CVE_CHECK_DB_NAME= "cvelist"meta/recipes-devtools/sbom-cve-check/sbom-cve-check-update-cvelist-native_2026-05-07.bb renamed from meta/recipes-devtools/sbom-cve-check/sbom-cve-check-update-cvelist-native.bb +1
-1-# cve_2026-05-07_1300Z SRCREV = "dd0e93c75034d0167498174c886a56729edc44de" +UPSTREAM_CHECK_GITTAGREGEX = "(?P<pver>.+)_baseline" require sbom-cve-check-update-db.inc(quoted diff) +0
-0native.bb b/meta/recipes-devtools/sbom-cve-check/sbom-cve-check-update-nvd- native_2026.05.07-000006.bb
similarity index 90%
rename from meta/recipes-devtools/sbom-cve-check/sbom-cve-check-update- nvd-native.bb
rename to meta/recipes-devtools/sbom-cve-check/sbom-cve-check-update-nvd- native_2026.05.07-000006.bb
index26a14e6eb1..02446e30ce100644
--- a/meta/recipes-devtools/sbom-cve-check/sbom-cve-check-update-nvd- native.bb
+++ b/meta/recipes-devtools/sbom-cve-check/sbom-cve-check-update-nvd- native_2026.05.07-000006.bb(quoted diff) +0
-0@@ -6,7 +6,7 @@ HOMEPAGE = "https://github.com/fkie-cad/nvd-json-data-feeds"
SRC_URI= "git://github.com/fkie-cad/nvd-json-data-
feeds.git;branch=main;protocol=https;destsuffix="
SBOM_CVE_CHECK_DB_NAME= "nvd-fkie"meta/recipes-devtools/sbom-cve-check/sbom-cve-check-update-nvd-native_2026.05.07-000006.bb renamed from meta/recipes-devtools/sbom-cve-check/sbom-cve-check-update-nvd-native.bb +1
-2-# v2026.05.07-000006 SRCREV = "72d8841c8ad9083ebf6723063f275444ea0d76f9" +UPSTREAM_CHECK_GITTAGREGEX = "v(?P<pver>.+)" require sbom-cve-check-update-db.inc --2.47.3
Quoted 2 lines · Peter
This is probably old commit message that claims PV being 1.0.
I can see version provided in filename of recipes being updated in this commit.
The commit updates the filenames from not including a version to including a version, and is based on current oe-core master. Do you see something different?
Alex
Quoted 12 lines
-----Original Message-----
From: Alexander Kanavin <[email protected]>
Sent: Tuesday, May 12, 2026 12:24 PM
To: Marko, Peter (FT D EU SK BFS1) <[email protected]>
Cc: [email protected]; Alexander Kanavin <[email protected]>
Subject: Re: [OE-core] [PATCH] sbom-cve-check: set PV from upstream tags and ensure version checks are correctOn Tue, 12 May 2026 at 12:14, Marko, Peter <[email protected]> wrote:
Quoted 8 lines
Quoted 2 lines
This is probably old commit message that claims PV being 1.0.
I can see version provided in filename of recipes being updated in this commit.The commit updates the filenames from not including a version to including a version, and is based on current oe-core master. Do you see something different?
Alex
My bad, sorry.
The original names were shortend with ...