Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Peter Marko <peter.marko@siemens.com>
To: openembedded-core@lists.openembedded.org
Cc: peter.marko@siemens.com
Subject: [wrynose][RFC PATCH 06/11] sbom-cve-check-update-nvd-native: update to version 2026.06.24-000003
Date: Sat,  8 Aug 2026 12:51:42 +0200	[thread overview]
Message-ID: <20260808105147.42294-7-peter.marko@siemens.com> (raw)
In-Reply-To: <20260808105147.42294-1-peter.marko@siemens.com>

From: "Benjamin Robin (Schneider Electric)" <benjamin.robin@bootlin.com>

Update fkie-cad/nvd-json-data-feeds to the CVE database from 2026-06-24.

Signed-off-by: Benjamin Robin (Schneider Electric) <benjamin.robin@bootlin.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
(From OE-Core rev: fba290297e9bbc8c6c4086e7784ece5d06dbd26d)
Signed-off-by: Peter Marko <peter.marko@siemens.com>
---
 ...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%)

diff --git a/meta/recipes-devtools/sbom-cve-check/sbom-cve-check-update-nvd-native_2026.06.09-000006.bb b/meta/recipes-devtools/sbom-cve-check/sbom-cve-check-update-nvd-native_2026.06.24-000003.bb
similarity index 89%
rename from meta/recipes-devtools/sbom-cve-check/sbom-cve-check-update-nvd-native_2026.06.09-000006.bb
rename to meta/recipes-devtools/sbom-cve-check/sbom-cve-check-update-nvd-native_2026.06.24-000003.bb
index 2917c89e62..73d9e77692 100644
--- a/meta/recipes-devtools/sbom-cve-check/sbom-cve-check-update-nvd-native_2026.06.09-000006.bb
+++ b/meta/recipes-devtools/sbom-cve-check/sbom-cve-check-update-nvd-native_2026.06.24-000003.bb
@@ -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


  parent reply	other threads:[~2026-08-08 10:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-08 10:51 [wrynose][RFC PATCH 00/11] sbom-cve-check update Peter Marko
2026-08-08 10:51 ` [wrynose][RFC PATCH 01/11] sbom-cve-check-update-nvd-native: upgrade 2026.05.07-000006 -> 2026.06.09-000006 Peter Marko
2026-08-08 10:51 ` [wrynose][RFC PATCH 02/11] python3-shacl2code: upgrade 1.0.1 -> 1.1.0 Peter Marko
2026-08-08 10:51 ` [wrynose][RFC PATCH 03/11] python3-spdx-python-model: update from version 0.0.5 to 0.0.6 Peter Marko
2026-08-08 10:51 ` [wrynose][RFC PATCH 04/11] python3-sbom-cve-check: update to version 1.3.2 Peter Marko
2026-08-08 10:51 ` [wrynose][RFC PATCH 05/11] sbom-cve-check-update-cvelist-native: update to version 2026-06-24 Peter Marko
2026-08-08 10:51 ` Peter Marko [this message]
2026-08-08 10:51 ` [wrynose][RFC PATCH 07/11] sbom-cve-check-update-cvelist-native: -> 2026-07-23 Peter Marko
2026-08-08 10:51 ` [wrynose][RFC PATCH 08/11] sbom-cve-check-update-nvd-native: -> 2026.07.23-000007 Peter Marko
2026-08-08 10:51 ` [wrynose][RFC PATCH 09/11] python3-sbom-cve-check: update to version 1.3.3 Peter Marko
2026-08-08 10:51 ` [wrynose][RFC PATCH 10/11] sbom-cve-check-update-cvelist-native: update to version 2026-08-03 Peter Marko
2026-08-08 10:51 ` [wrynose][RFC PATCH 11/11] sbom-cve-check-update-nvd-native: update to version 2026.08.03-000011 Peter Marko

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=20260808105147.42294-7-peter.marko@siemens.com \
    --to=peter.marko@siemens.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