sbom-cve-check update
cover sbom-cve-check update
This series updates sbom-cve-check tooling in wrynose to current master. Unfortunately it shows that having cve-check tooling in upstream components violates LTS patch acceptance policies.
In this case the most visible is python3-shacl2code (1.0.1 -> 1.1.0), but also sbom-cve-check-update-nvd-native introduces new features (which is actually the reason why this upgrade is wanted). For now this should not be a big issue as all the dependencies are very new and used exclusively in cve-check, however by time they may be used in other recipes or tooling, too.
So I am sending this series as RFC to discuss future of CVE checking on LTS branches.
* should we go with this series as is (possibly updating policy text)?
* or are we stuck with old code for next 3.5 years?
* or separate the tooling to meta-sbom-cve-check which would only have master branch to service all currently supported releases?
* or create mixins layer (to be also used by AB cve-metrics jobs)?
* or are there some other suggestions how to rework this series?
My preference would be to have cve-check aligned for all supported releases (even scarthgap), so I would welcome opinions and discussion on this topic.
Alexander Kanavin (1):
python3-shacl2code: upgrade 1.0.1 -> 1.1.0
Benjamin Robin (3):
python3-sbom-cve-check: update to version 1.3.3 sbom-cve-check-update-cvelist-native: update to version 2026-08-03 sbom-cve-check-update-nvd-native: update to version 2026.08.03-000011
Benjamin Robin (Schneider Electric) (4):
python3-spdx-python-model: update from version 0.0.5 to 0.0.6
python3-sbom-cve-check: update to version 1.3.2 sbom-cve-check-update-cvelist-native: update to version 2026-06-24 sbom-cve-check-update-nvd-native: update to version 2026.06.24-000003
Tim Orling (2):
sbom-cve-check-update-cvelist-native: -> 2026-07-23 sbom-cve-check-update-nvd-native: -> 2026.07.23-000007
Wang Mingyu (1):
sbom-cve-check-update-nvd-native: upgrade 2026.05.07-000006 ->
2026.06.09-000006
...{python3-shacl2code_1.0.1.bb => python3-shacl2code_1.1.0.bb} | 2 +-
...python-model_0.0.5.bb => python3-spdx-python-model_0.0.6.bb} | 2 +-
...-sbom-cve-check_1.3.1.bb => python3-sbom-cve-check_1.3.3.bb} | 2 +-
...07.bb => sbom-cve-check-update-cvelist-native_2026-08-03.bb} | 2 +-
...bb => sbom-cve-check-update-nvd-native_2026.08.03-000011.bb} | 2 +-
5 files changed, 5 insertions(+), 5 deletions(-)
rename meta/recipes-devtools/python/{python3-shacl2code_1.0.1.bb => python3-shacl2code_1.1.0.bb} (81%)
rename meta/recipes-devtools/python/{python3-spdx-python-model_0.0.5.bb => python3-spdx-python-model_0.0.6.bb} (93%)
rename meta/recipes-devtools/sbom-cve-check/{python3-sbom-cve-check_1.3.1.bb => python3-sbom-cve-check_1.3.3.bb} (82%)
rename meta/recipes-devtools/sbom-cve-check/{sbom-cve-check-update-cvelist-native_2026-05-07.bb => sbom-cve-check-update-cvelist-native_2026-08-03.bb} (89%)
rename meta/recipes-devtools/sbom-cve-check/{sbom-cve-check-update-nvd-native_2026.05.07-000006.bb => sbom-cve-check-update-nvd-native_2026.08.03-000011.bb} (89%)RFC PATCH 1/11 sbom-cve-check-update-nvd-native: upgrade 2026.05.07-000006 -> 2026.06.09-000006
From: Wang Mingyu <[email protected]>
(From OE-Core rev: d33c73535229b5066901faedaaaca0aa6bbd99bf)
---
...bb => sbom-cve-check-update-nvd-native_2026.06.09-000006.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-devtools/sbom-cve-check/{sbom-cve-check-update-nvd-native_2026.05.07-000006.bb => sbom-cve-check-update-nvd-native_2026.06.09-000006.bb} (89%)meta/recipes-devtools/sbom-cve-check/sbom-cve-check-update-nvd-native_2026.06.09-000006.bb renamed from meta/recipes-devtools/sbom-cve-check/sbom-cve-check-update-nvd-native_2026.05.07-000006.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" -SRCREV = "72d8841c8ad9083ebf6723063f275444ea0d76f9" +SRCREV = "7ff4a0622bfdf5313c79635951112d2a45bbe9fd" UPSTREAM_CHECK_GITTAGREGEX = "v(?P<pver>.+)" require sbom-cve-check-update-db.inc
RFC PATCH 2/11 python3-shacl2code: upgrade 1.0.1 -> 1.1.0
In reply to Peter MarkoFrom: Alexander Kanavin <[email protected]>
Add a patch to python3-spdx-python-model to support this release.
(From OE-Core rev: f6557000abc90b0c3b7ca5b4560849e64425c853)
---
...e_1.0.1.bb => python3-shacl2code_1.1.0.bb} | 2 +-
...pdate-shacl2code-to-1.1.0-and-add-ke.patch | 41 +++++++++++++++++++
.../python/python3-spdx-python-model_0.0.5.bb | 10 ++---
3 files changed, 47 insertions(+), 6 deletions(-)
rename meta/recipes-devtools/python/{python3-shacl2code_1.0.1.bb => python3-shacl2code_1.1.0.bb} (81%)
create mode 100644 meta/recipes-devtools/python/python3-spdx-python-model/0001-pyproject.toml-Update-shacl2code-to-1.1.0-and-add-ke.patchmeta/recipes-devtools/python/python3-shacl2code_1.1.0.bb renamed from meta/recipes-devtools/python/python3-shacl2code_1.0.1.bb +1 -1
@@ -5,7 +5,7 @@ LICENSE = "MIT" LIC_FILES_CHKSUM = "file://LICENSE;md5=0582f358628f299f29c23bf5fb2f73c9" PYPI_PACKAGE = "shacl2code" -SRC_URI[sha256sum] = "c856822b40c330452b8b31e94a658ad4595a5ef03cdb75ea432ea9c73d0cf7d9" +SRC_URI[sha256sum] = "0f3a243c6482a0f95c5a793288d304908506b51b82dc6133de22be477cd75c24" inherit pypi python_hatchling
meta/recipes-devtools/python/python3-spdx-python-model/0001-pyproject.toml-Update-shacl2code-to-1.1.0-and-add-ke.patch new file +41 -0
41 lines not on this page · raw message
meta/recipes-devtools/python/python3-spdx-python-model_0.0.5.bb +5 -5
@@ -7,11 +7,11 @@ LIC_FILES_CHKSUM = "file://LICENSE;md5=86d3f3a95c324c9479bd8986968f4327" PYPI_PACKAGE = "spdx_python_model" SRC_URI[sha256sum] = "4bcf7c6e5e2e8f0b787ed4eb8fb519e2ed776e820cb6d9eb93e44e98eb92ca2d" -SRC_URI += " \ - https://spdx.org/rdf/3.0.1/spdx-context.jsonld;name=spdx1 \ - https://spdx.org/rdf/3.0.1/spdx-json-serialize-annotations.ttl;name=spdx2 \ - https://spdx.org/rdf/3.0.1/spdx-model.ttl;name=spdx3 \ -" +SRC_URI += "https://spdx.org/rdf/3.0.1/spdx-context.jsonld;name=spdx1 \ + https://spdx.org/rdf/3.0.1/spdx-json-serialize-annotations.ttl;name=spdx2 \ + https://spdx.org/rdf/3.0.1/spdx-model.ttl;name=spdx3 \ + file://0001-pyproject.toml-Update-shacl2code-to-1.1.0-and-add-ke.patch \ + " SRC_URI[spdx1.sha256sum] = "c72b0928f094c83e5c127784edb1ebca2af74a104fcacc007c332b23cbc788bd" SRC_URI[spdx2.sha256sum] = "c6a54b51230eb2bf3b31302546af201f303e0b7931c1db404d7f5b72b6f863e6"
RFC PATCH 3/11 python3-spdx-python-model: update from version 0.0.5 to 0.0.6
In reply to Peter MarkoFrom: "Benjamin Robin (Schneider Electric)" <[email protected]>
Drop the patch which should no longer be necessary. This is a partial revert of f6557000abc90b0c3b7ca5b4560849e64425c853
(From OE-Core rev: 9b5c92cd6b8ef8a56ebc3815120fd4af5872173c)
---
...pdate-shacl2code-to-1.1.0-and-add-ke.patch | 41 -------------------
....bb => python3-spdx-python-model_0.0.6.bb} | 12 +++---
2 files changed, 6 insertions(+), 47 deletions(-)
delete mode 100644 meta/recipes-devtools/python/python3-spdx-python-model/0001-pyproject.toml-Update-shacl2code-to-1.1.0-and-add-ke.patch
rename meta/recipes-devtools/python/{python3-spdx-python-model_0.0.5.bb => python3-spdx-python-model_0.0.6.bb} (72%)meta/recipes-devtools/python/python3-spdx-python-model/0001-pyproject.toml-Update-shacl2code-to-1.1.0-and-add-ke.patch deleted +0 -41
@@ -1,41 +0,0 @@ -From b623473f634aebeb30028cc746fb7a3da4fb2ce3 Mon Sep 17 00:00:00 2001 -From: Arthit Suriyawongkul <[email protected]> -Date: Sat, 6 Jun 2026 02:44:48 +0100 -Subject: [PATCH] pyproject.toml: Update shacl2code to 1.1.0 and add keywords - (#35) - -Signed-off-by: Arthit Suriyawongkul <[email protected]> -Upstream-Status: Backport [https://github.com/spdx/spdx-python-model/commit/2d7b71a7c8e6270a1c8795cdeb4f3dcd9393b3a9] -Signed-off-by: Alexander Kanavin <[email protected]> ---- - pyproject.toml | 10 +++++++++- - 1 file changed, 9 insertions(+), 1 deletion(-) - -diff --git a/pyproject.toml b/pyproject.toml -index c8b3e56..df011e8 100644 ---- a/pyproject.toml -+++ b/pyproject.toml -@@ -8,6 +8,14 @@ authors = [ - {name = "Joshua Watt", email = "[email protected]"}, - ] - readme = "README.md" -+keywords = [ -+ "spdx", -+ "sbom", -+ "spdx3", -+ "software-bill-of-materials", -+ "shacl2code", -+ "bindings", -+] - classifiers = [ - "Development Status :: 4 - Beta", - "Intended Audience :: Developers", -@@ -36,7 +44,7 @@ Issues = "https://github.com/spdx/spdx-python-model/issues" - requires = [ - "hatchling >= 1.27.0", - "hatch-build-scripts >= 0.0.4", -- "shacl2code == 1.0.1", -+ "shacl2code == 1.1.0", - ] - build-backend = "hatchling.build" -
meta/recipes-devtools/python/python3-spdx-python-model_0.0.6.bb renamed from meta/recipes-devtools/python/python3-spdx-python-model_0.0.5.bb +6 -6
@@ -5,13 +5,13 @@ LICENSE = "Apache-2.0" LIC_FILES_CHKSUM = "file://LICENSE;md5=86d3f3a95c324c9479bd8986968f4327" PYPI_PACKAGE = "spdx_python_model" -SRC_URI[sha256sum] = "4bcf7c6e5e2e8f0b787ed4eb8fb519e2ed776e820cb6d9eb93e44e98eb92ca2d" +SRC_URI[sha256sum] = "f1938eb08d08218278122849bba123b8993a0171e9b4f5ea6af7aeb71f3204d7" -SRC_URI += "https://spdx.org/rdf/3.0.1/spdx-context.jsonld;name=spdx1 \ - https://spdx.org/rdf/3.0.1/spdx-json-serialize-annotations.ttl;name=spdx2 \ - https://spdx.org/rdf/3.0.1/spdx-model.ttl;name=spdx3 \ - file://0001-pyproject.toml-Update-shacl2code-to-1.1.0-and-add-ke.patch \ - " +SRC_URI += " \ + https://spdx.org/rdf/3.0.1/spdx-context.jsonld;name=spdx1 \ + https://spdx.org/rdf/3.0.1/spdx-json-serialize-annotations.ttl;name=spdx2 \ + https://spdx.org/rdf/3.0.1/spdx-model.ttl;name=spdx3 \ +" SRC_URI[spdx1.sha256sum] = "c72b0928f094c83e5c127784edb1ebca2af74a104fcacc007c332b23cbc788bd" SRC_URI[spdx2.sha256sum] = "c6a54b51230eb2bf3b31302546af201f303e0b7931c1db404d7f5b72b6f863e6"
RFC PATCH 4/11 python3-sbom-cve-check: update to version 1.3.2
In reply to Peter MarkoFrom: "Benjamin Robin (Schneider Electric)" <[email protected]>
For details on this new release, see:
https://github.com/bootlin/sbom-cve-check/releases/tag/v1.3.2
(From OE-Core rev: cd6313d94ac221dc37c30ffec8c83b6c8d1deeff)
---
...-sbom-cve-check_1.3.1.bb => python3-sbom-cve-check_1.3.2.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-devtools/sbom-cve-check/{python3-sbom-cve-check_1.3.1.bb => python3-sbom-cve-check_1.3.2.bb} (82%)meta/recipes-devtools/sbom-cve-check/python3-sbom-cve-check_1.3.2.bb renamed from meta/recipes-devtools/sbom-cve-check/python3-sbom-cve-check_1.3.1.bb +1 -1
@@ -5,7 +5,7 @@ LICENSE = "GPL-2.0-or-later" LIC_FILES_CHKSUM = "file://LICENSE;md5=570a9b3749dd0463a1778803b12a6dce" PYPI_PACKAGE = "sbom_cve_check" -SRC_URI[sha256sum] = "675828b2f02f11620b7a229853a24d09264bf41161be5fbb80a92456f46a14e0" +SRC_URI[sha256sum] = "0a7f07a0c6ce45d40adc6d311ddc25c4466f59bafcbce149b6fb3663791a5d89" inherit pypi python_hatchling
RFC PATCH 5/11 sbom-cve-check-update-cvelist-native: update to version 2026-06-24
In reply to Peter MarkoFrom: "Benjamin Robin (Schneider Electric)" <[email protected]>
Update cvelistV5 to the CVE database from 2026-06-24.
(From OE-Core rev: f7a706321eb783ad43d8d9666ea3536024cb5be8)
---
...07.bb => sbom-cve-check-update-cvelist-native_2026-06-24.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-devtools/sbom-cve-check/{sbom-cve-check-update-cvelist-native_2026-05-07.bb => sbom-cve-check-update-cvelist-native_2026-06-24.bb} (89%)meta/recipes-devtools/sbom-cve-check/sbom-cve-check-update-cvelist-native_2026-06-24.bb renamed from meta/recipes-devtools/sbom-cve-check/sbom-cve-check-update-cvelist-native_2026-05-07.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" -SRCREV = "dd0e93c75034d0167498174c886a56729edc44de" +SRCREV = "966bddf787997b471325e065cae82702a60c64ff" UPSTREAM_CHECK_GITTAGREGEX = "(?P<pver>.+)_baseline" require sbom-cve-check-update-db.inc
RFC PATCH 6/11 sbom-cve-check-update-nvd-native: update to version 2026.06.24-000003
In reply to Peter MarkoFrom: "Benjamin Robin (Schneider Electric)" <[email protected]>
Update fkie-cad/nvd-json-data-feeds to the CVE database from 2026-06-24.
(From OE-Core rev: fba290297e9bbc8c6c4086e7784ece5d06dbd26d)
---
...bb => sbom-cve-check-update-nvd-native_2026.06.24-000003.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-devtools/sbom-cve-check/{sbom-cve-check-update-nvd-native_2026.06.09-000006.bb => sbom-cve-check-update-nvd-native_2026.06.24-000003.bb} (89%)meta/recipes-devtools/sbom-cve-check/sbom-cve-check-update-nvd-native_2026.06.24-000003.bb renamed from meta/recipes-devtools/sbom-cve-check/sbom-cve-check-update-nvd-native_2026.06.09-000006.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" -SRCREV = "7ff4a0622bfdf5313c79635951112d2a45bbe9fd" +SRCREV = "11e62eba27133a54836b7a081d05ff96f72d879b" UPSTREAM_CHECK_GITTAGREGEX = "v(?P<pver>.+)" require sbom-cve-check-update-db.inc
RFC PATCH 7/11 sbom-cve-check-update-cvelist-native: -> 2026-07-23
In reply to Peter MarkoFrom: Tim Orling <[email protected]>
The diff is quite large, but a partial comparison can be seen:
https://github.com/CVEProject/cvelistV5/compare/2026-06-24_baseline..2026-07-23_baseline
(From OE-Core rev: 1323691ceab2a338c4d5b9c15624b8d22c472e7f)
---
...24.bb => sbom-cve-check-update-cvelist-native_2026-07-23.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-devtools/sbom-cve-check/{sbom-cve-check-update-cvelist-native_2026-06-24.bb => sbom-cve-check-update-cvelist-native_2026-07-23.bb} (89%)meta/recipes-devtools/sbom-cve-check/sbom-cve-check-update-cvelist-native_2026-07-23.bb renamed from meta/recipes-devtools/sbom-cve-check/sbom-cve-check-update-cvelist-native_2026-06-24.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" -SRCREV = "966bddf787997b471325e065cae82702a60c64ff" +SRCREV = "7a274ec07043f54c07d0a3b5c7fc89ba5793f023" UPSTREAM_CHECK_GITTAGREGEX = "(?P<pver>.+)_baseline" require sbom-cve-check-update-db.inc
RFC PATCH 8/11 sbom-cve-check-update-nvd-native: -> 2026.07.23-000007
In reply to Peter MarkoFrom: Tim Orling <[email protected]>
The diff is quite large, but a partial comparison can be seen:
https://github.com/fkie-cad/nvd-json-data-feeds/compare/v2026.06.24-000003..v2026.07.23-000007
(From OE-Core rev: 9d89b3b802bab144afa30e03b0411ae58232ef11)
---
...bb => sbom-cve-check-update-nvd-native_2026.07.23-000007.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-devtools/sbom-cve-check/{sbom-cve-check-update-nvd-native_2026.06.24-000003.bb => sbom-cve-check-update-nvd-native_2026.07.23-000007.bb} (89%)meta/recipes-devtools/sbom-cve-check/sbom-cve-check-update-nvd-native_2026.07.23-000007.bb renamed from meta/recipes-devtools/sbom-cve-check/sbom-cve-check-update-nvd-native_2026.06.24-000003.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" -SRCREV = "11e62eba27133a54836b7a081d05ff96f72d879b" +SRCREV = "64a0cea215628d780438fba8bfe0f3300db1b702" UPSTREAM_CHECK_GITTAGREGEX = "v(?P<pver>.+)" require sbom-cve-check-update-db.inc
RFC PATCH 9/11 python3-sbom-cve-check: update to version 1.3.3
In reply to Peter MarkoFrom: Benjamin Robin <[email protected]>
For details on this new release, see:
https://github.com/bootlin/sbom-cve-check/releases/tag/v1.3.3
(From OE-Core rev: 7feb4e30ba17a4b0eb37a1c6dde671d4491bd35d)
---
...-sbom-cve-check_1.3.2.bb => python3-sbom-cve-check_1.3.3.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-devtools/sbom-cve-check/{python3-sbom-cve-check_1.3.2.bb => python3-sbom-cve-check_1.3.3.bb} (82%)meta/recipes-devtools/sbom-cve-check/python3-sbom-cve-check_1.3.3.bb renamed from meta/recipes-devtools/sbom-cve-check/python3-sbom-cve-check_1.3.2.bb +1 -1
@@ -5,7 +5,7 @@ LICENSE = "GPL-2.0-or-later" LIC_FILES_CHKSUM = "file://LICENSE;md5=570a9b3749dd0463a1778803b12a6dce" PYPI_PACKAGE = "sbom_cve_check" -SRC_URI[sha256sum] = "0a7f07a0c6ce45d40adc6d311ddc25c4466f59bafcbce149b6fb3663791a5d89" +SRC_URI[sha256sum] = "8b766be1ae92b4eceaa2f694dd4724e310886c6436f44267a6bbc6a7b81ab8b9" inherit pypi python_hatchling
RFC PATCH 10/11 sbom-cve-check-update-cvelist-native: update to version 2026-08-03
In reply to Peter MarkoFrom: Benjamin Robin <[email protected]>
Update cvelistV5 to the CVE database from 2026-08-03.
(From OE-Core rev: 25e68deb8178f7021605a39fa85acea04a375372)
---
...23.bb => sbom-cve-check-update-cvelist-native_2026-08-03.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-devtools/sbom-cve-check/{sbom-cve-check-update-cvelist-native_2026-07-23.bb => sbom-cve-check-update-cvelist-native_2026-08-03.bb} (89%)meta/recipes-devtools/sbom-cve-check/sbom-cve-check-update-cvelist-native_2026-08-03.bb renamed from meta/recipes-devtools/sbom-cve-check/sbom-cve-check-update-cvelist-native_2026-07-23.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" -SRCREV = "7a274ec07043f54c07d0a3b5c7fc89ba5793f023" +SRCREV = "b160e6f2915ac726b29ee0689fc920f5016abef5" UPSTREAM_CHECK_GITTAGREGEX = "(?P<pver>.+)_baseline" require sbom-cve-check-update-db.inc
RFC PATCH 11/11 sbom-cve-check-update-nvd-native: update to version 2026.08.03-000011
In reply to Peter MarkoFrom: Benjamin Robin <[email protected]>
Update fkie-cad/nvd-json-data-feeds to the CVE database from 2026.08.03.
(From OE-Core rev: 5928cf1985d65b5dc7a909df596d7ff91533fccd)
---
...bb => sbom-cve-check-update-nvd-native_2026.08.03-000011.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-devtools/sbom-cve-check/{sbom-cve-check-update-nvd-native_2026.07.23-000007.bb => sbom-cve-check-update-nvd-native_2026.08.03-000011.bb} (89%)meta/recipes-devtools/sbom-cve-check/sbom-cve-check-update-nvd-native_2026.08.03-000011.bb renamed from meta/recipes-devtools/sbom-cve-check/sbom-cve-check-update-nvd-native_2026.07.23-000007.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" -SRCREV = "64a0cea215628d780438fba8bfe0f3300db1b702" +SRCREV = "b9f52bb052695dac5cabbd58e049eaac73697161" UPSTREAM_CHECK_GITTAGREGEX = "v(?P<pver>.+)" require sbom-cve-check-update-db.inc
Quoted 24 lines · Peter Marko
This series updates sbom-cve-check tooling in wrynose to current master. Unfortunately it shows that having cve-check tooling in upstream components violates LTS patch acceptance policies.
In this case the most visible is python3-shacl2code (1.0.1 -> 1.1.0), but also sbom-cve-check-update-nvd-native introduces new features (which is actually the reason why this upgrade is wanted). For now this should not be a big issue as all the dependencies are very new and used exclusively in cve-check, however by time they may be used in other recipes or tooling, too.
So I am sending this series as RFC to discuss future of CVE checking on LTS branches.
* should we go with this series as is (possibly updating policy text)?
* or are we stuck with old code for next 3.5 years?
* or separate the tooling to meta-sbom-cve-check which would only have master branch to service all currently supported releases?
* or create mixins layer (to be also used by AB cve-metrics jobs)?
* or are there some other suggestions how to rework this series?My preference would be to have cve-check aligned for all supported releases (even scarthgap), so I would welcome opinions and discussion on this topic.
Quoted 5 lines
Cc Richard Purdie <[email protected]>Cc Benjamin Robin <[email protected]>Cc Yoann Congal <[email protected]>Cc Paul Barker <[email protected]>Cc Ross Burton <[email protected]>
Hi Peter,
The TSC has discussed this series and is happy for sbom-cve-check to be updated on wrynose. It's in line with the expectations we had when wrynose was released, and the upstream maintainer is involved.
For scarthgap it's a different question. That still has the cve-check.bbclass implementation instead of sbom-cve-check, this would be whole new framework rather than a set of updates. I wonder if this can be handled via an LTS mixin layer instead of a backport in OE-core?
Best regards,
Signature · 1 line
Paul Barker
Quoted 21 lines · Paul Barker
Quoted 20 lines · Peter Marko
This series updates sbom-cve-check tooling in wrynose to current master. Unfortunately it shows that having cve-check tooling in upstream components violates LTS patch acceptance policies.
In this case the most visible is python3-shacl2code (1.0.1 -> 1.1.0), but also sbom-cve-check-update-nvd-native introduces new features (which is actually the reason why this upgrade is wanted). For now this should not be a big issue as all the dependencies are very new and used exclusively in cve-check, however by time they may be used in other recipes or tooling, too.
So I am sending this series as RFC to discuss future of CVE checking on LTS branches.
* should we go with this series as is (possibly updating policy text)?
* or are we stuck with old code for next 3.5 years?
* or separate the tooling to meta-sbom-cve-check which would only have master branch to service all currently supported releases?
* or create mixins layer (to be also used by AB cve-metrics jobs)?
* or are there some other suggestions how to rework this series?
Quoted 3 lines
Quoted 3 lines
My preference would be to have cve-check aligned for all supported releases (even scarthgap), so I would welcome opinions and discussion on this topic.
Hello Peter,
Thank you for taking the time to create this series. I had been planning to work on it, but I was a bit busy :)
Quoted 11 lines
Hi Peter,
The TSC has discussed this series and is happy for sbom-cve-check to be updated on wrynose. It's in line with the expectations we had when wrynose was released, and the upstream maintainer is involved.
For scarthgap it's a different question. That still has the cve-check.bbclass implementation instead of sbom-cve-check, this would be whole new framework rather than a set of updates. I wonder if this can be handled via an LTS mixin layer instead of a backport in OE-core?
Hello Paul,
Technically, I think we could backport sbom-cve-check to scarthgap, but indeed it still has the cve-check.bbclass implementation.
sbom-cve-check can be run outside of Yocto, but if you want it integrated into Yocto, there's already a layer for that:
https://github.com/bootlin/meta-sbom-cve-check
However, I need to update it to version 1.3.3.
Signature · 3 lines
Benjamin Robin, Bootlin Embedded Linux and Kernel engineering https://bootlin.com
Quoted 33 lines
-----Original Message-----
From: Benjamin Robin <[email protected]>
Sent: Thursday, August 13, 2026 1:56 PM
To: Marko, Peter (FT D EU SK BFS1) <[email protected]>; [email protected]; Paul Barker <[email protected]>
Cc: Richard Purdie <[email protected]>; Yoann Congal <[email protected]>; Ross Burton <[email protected]>
Subject: Re: [wrynose][RFC PATCH 00/11] sbom-cve-check updateQuoted 21 lines · Paul Barker
Quoted 20 lines · Peter Marko
This series updates sbom-cve-check tooling in wrynose to current master. Unfortunately it shows that having cve-check tooling in upstream components violates LTS patch acceptance policies.
In this case the most visible is python3-shacl2code (1.0.1 -> 1.1.0), but also sbom-cve-check-update-nvd-native introduces new features (which is actually the reason why this upgrade is wanted). For now this should not be a big issue as all the dependencies are very new and used exclusively in cve-check, however by time they may be used in other recipes or tooling, too.
So I am sending this series as RFC to discuss future of CVE checking on LTS branches.
* should we go with this series as is (possibly updating policy text)?
* or are we stuck with old code for next 3.5 years?
* or separate the tooling to meta-sbom-cve-check which would only have master branch to service all currently supported releases?
* or create mixins layer (to be also used by AB cve-metrics jobs)?
* or are there some other suggestions how to rework this series?
Quoted 20 lines
Quoted 3 lines
Quoted 3 lines
My preference would be to have cve-check aligned for all supported releases (even scarthgap), so I would welcome opinions and discussion on this topic.
Hello Peter,
Thank you for taking the time to create this series. I had been planning to work on it, but I was a bit busy :)
Quoted 11 lines
Hi Peter,
The TSC has discussed this series and is happy for sbom-cve-check to be updated on wrynose. It's in line with the expectations we had when wrynose was released, and the upstream maintainer is involved.
For scarthgap it's a different question. That still has the cve-check.bbclass implementation instead of sbom-cve-check, this would be whole new framework rather than a set of updates. I wonder if this can be handled via an LTS mixin layer instead of a backport in OE-core?
Paul,
as the meta-sbom-cve-check layer shows, sbom-cve-check can co-exist with the old cve-check. It does not have to be the super-invasive with breaking change.
So in theory it should be pretty easy to copy 3 classes and bunch of support recipes. But I'm also fine with having an external layer for that.
Question is if Yocto project would also switch cve-metrics to the sbom-cve-check.
That would of course highly increase the open CVE numbers but would also help identify missing CVE fixes.
Quoted 9 lines
Hello Paul,
Technically, I think we could backport sbom-cve-check to scarthgap, but indeed it still has the cve-check.bbclass implementation.
sbom-cve-check can be run outside of Yocto, but if you want it integrated into Yocto, there's already a layer for that:
https://github.com/bootlin/meta-sbom-cve-check
Benjamin,
This is super cool.
However, cve-metrics uses sbom-cve-check-recipe, which is not part of this layer. When updating, please consider adding it.
Peter
Quoted 9 lines
However, I need to update it to version 1.3.3.
--
Benjamin Robin, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
Quoted 64 lines · Peter
Quoted 22 lines · Paul Barker
Quoted 21 lines · Peter Marko
Quoted 20 lines
This series updates sbom-cve-check tooling in wrynose to current master. Unfortunately it shows that having cve-check tooling in upstream components violates LTS patch acceptance policies.
In this case the most visible is python3-shacl2code (1.0.1 -> 1.1.0), but also sbom-cve-check-update-nvd-native introduces new features (which is actually the reason why this upgrade is wanted). For now this should not be a big issue as all the dependencies are very new and used exclusively in cve-check, however by time they may be used in other recipes or tooling, too.
So I am sending this series as RFC to discuss future of CVE checking on LTS branches.
* should we go with this series as is (possibly updating policy text)?
* or are we stuck with old code for next 3.5 years?
* or separate the tooling to meta-sbom-cve-check which would only have master branch to service all currently supported releases?
* or create mixins layer (to be also used by AB cve-metrics jobs)?
* or are there some other suggestions how to rework this series?Quoted 20 lines
Quoted 3 lines
Quoted 3 lines
My preference would be to have cve-check aligned for all supported releases (even scarthgap), so I would welcome opinions and discussion on this topic.
Hello Peter,
Thank you for taking the time to create this series. I had been planning to work on it, but I was a bit busy :)
Quoted 11 lines
Hi Peter,
The TSC has discussed this series and is happy for sbom-cve-check to be updated on wrynose. It's in line with the expectations we had when wrynose was released, and the upstream maintainer is involved.
For scarthgap it's a different question. That still has the cve-check.bbclass implementation instead of sbom-cve-check, this would be whole new framework rather than a set of updates. I wonder if this can be handled via an LTS mixin layer instead of a backport in OE-core?
Paul,
as the meta-sbom-cve-check layer shows, sbom-cve-check can co-exist with the old cve-check. It does not have to be the super-invasive with breaking change.
So in theory it should be pretty easy to copy 3 classes and bunch of support recipes. But I'm also fine with having an external layer for that.
Question is if Yocto project would also switch cve-metrics to the sbom-cve-check.
That would of course highly increase the open CVE numbers but would also help identify missing CVE fixes.Quoted 9 lines
Hello Paul,
Technically, I think we could backport sbom-cve-check to scarthgap, but indeed it still has the cve-check.bbclass implementation.
sbom-cve-check can be run outside of Yocto, but if you want it integrated into Yocto, there's already a layer for that:
https://github.com/bootlin/meta-sbom-cve-check
Quoted 7 lines
Benjamin,
This is super cool.
However, cve-metrics uses sbom-cve-check-recipe, which is not part of this layer. When updating, please consider adding it.Peter
Peter,
I will be on vacation, so I won’t have time to work on this. Feel free to create a PR to add this feature. I don't know if it's possible to simply add sbom-cve-check-recipe to Scarthgap—I haven't checked yet—but I have some slight doubts about it (though I could be completely wrong).
Signature · 3 lines
Benjamin Robin, Bootlin Embedded Linux and Kernel engineering https://bootlin.com
Hello Paul,
Since this was accepted within TSC, can this be picked to wrynose now? Or do I have to resend this series without RFC prefix?
Thanks,
Peter
Quoted 56 lines
-----Original Message-----
From: Paul Barker <[email protected]>
Sent: Thursday, August 13, 2026 1:46 PM
To: Marko, Peter (FT D EU SK BFS1) <[email protected]>; [email protected]
Cc: Richard Purdie <[email protected]>; Benjamin Robin <[email protected]>; Yoann Congal <[email protected]>; Ross Burton <[email protected]>
Subject: Re: [wrynose][RFC PATCH 00/11] sbom-cve-check updateQuoted 24 lines · Peter Marko
This series updates sbom-cve-check tooling in wrynose to current master. Unfortunately it shows that having cve-check tooling in upstream components violates LTS patch acceptance policies.
In this case the most visible is python3-shacl2code (1.0.1 -> 1.1.0), but also sbom-cve-check-update-nvd-native introduces new features (which is actually the reason why this upgrade is wanted). For now this should not be a big issue as all the dependencies are very new and used exclusively in cve-check, however by time they may be used in other recipes or tooling, too.
So I am sending this series as RFC to discuss future of CVE checking on LTS branches.
* should we go with this series as is (possibly updating policy text)?
* or are we stuck with old code for next 3.5 years?
* or separate the tooling to meta-sbom-cve-check which would only have master branch to service all currently supported releases?
* or create mixins layer (to be also used by AB cve-metrics jobs)?
* or are there some other suggestions how to rework this series?My preference would be to have cve-check aligned for all supported releases (even scarthgap), so I would welcome opinions and discussion on this topic.
Quoted 5 lines
Cc Richard Purdie <[email protected]>Cc Benjamin Robin <[email protected]>Cc Yoann Congal <[email protected]>Cc Paul Barker <[email protected]>Cc Ross Burton <[email protected]>Hi Peter,
The TSC has discussed this series and is happy for sbom-cve-check to be updated on wrynose. It's in line with the expectations we had when wrynose was released, and the upstream maintainer is involved.
For scarthgap it's a different question. That still has the cve-check.bbclass implementation instead of sbom-cve-check, this would be whole new framework rather than a set of updates. I wonder if this can be handled via an LTS mixin layer instead of a backport in OE-core?
Best regards,
--
Paul Barker
Quoted 4 lines · Peter Marko
Hello Paul,
Since this was accepted within TSC, can this be picked to wrynose now? Or do I have to resend this series without RFC prefix?
Hello,
I will take the series into review like this.
No need to resend.
Thanks!
Quoted 60 lines
Thanks,
PeterQuoted 56 lines
-----Original Message-----
From: Paul Barker <[email protected]>
Sent: Thursday, August 13, 2026 1:46 PM
To: Marko, Peter (FT D EU SK BFS1) <[email protected]>; [email protected]
Cc: Richard Purdie <[email protected]>; Benjamin Robin <[email protected]>; Yoann Congal <[email protected]>; Ross Burton <[email protected]>
Subject: Re: [wrynose][RFC PATCH 00/11] sbom-cve-check updateQuoted 24 lines · Peter Marko
This series updates sbom-cve-check tooling in wrynose to current master. Unfortunately it shows that having cve-check tooling in upstream components violates LTS patch acceptance policies.
In this case the most visible is python3-shacl2code (1.0.1 -> 1.1.0), but also sbom-cve-check-update-nvd-native introduces new features (which is actually the reason why this upgrade is wanted). For now this should not be a big issue as all the dependencies are very new and used exclusively in cve-check, however by time they may be used in other recipes or tooling, too.
So I am sending this series as RFC to discuss future of CVE checking on LTS branches.
* should we go with this series as is (possibly updating policy text)?
* or are we stuck with old code for next 3.5 years?
* or separate the tooling to meta-sbom-cve-check which would only have master branch to service all currently supported releases?
* or create mixins layer (to be also used by AB cve-metrics jobs)?
* or are there some other suggestions how to rework this series?My preference would be to have cve-check aligned for all supported releases (even scarthgap), so I would welcome opinions and discussion on this topic.
Quoted 5 lines
Cc Richard Purdie <[email protected]>Cc Benjamin Robin <[email protected]>Cc Yoann Congal <[email protected]>Cc Paul Barker <[email protected]>Cc Ross Burton <[email protected]>Hi Peter,
The TSC has discussed this series and is happy for sbom-cve-check to be updated on wrynose. It's in line with the expectations we had when wrynose was released, and the upstream maintainer is involved.
For scarthgap it's a different question. That still has the cve-check.bbclass implementation instead of sbom-cve-check, this would be whole new framework rather than a set of updates. I wonder if this can be handled via an LTS mixin layer instead of a backport in OE-core?
Best regards,
--
Paul Barker
Signature · 2 lines
Yoann Congal Smile ECS