From: Quentin Schulz <quentin.schulz@cherry.de>
To: peter.marko@siemens.com, docs@lists.yoctoproject.org
Subject: Re: [docs] [PATCH] vulnerabilities: update nvdcve file name
Date: Mon, 1 Sep 2025 11:50:36 +0200 [thread overview]
Message-ID: <44868213-2ff2-44bf-89a6-48e1dc6d3b80@cherry.de> (raw)
In-Reply-To: <20250824145316.1098911-1-peter.marko@siemens.com>
Hi Peter,
On 8/24/25 4:53 PM, Peter Marko via lists.yoctoproject.org wrote:
> From: Peter Marko <peter.marko@siemens.com>
>
> The filename is outdated as its version was already bumped and there are
> also different files for different feed choices.
> Use glob to match any available file.
>
When did this become possible? I see a new fetcher in
fb62c4c3dbca4e58f7ce6cf29d4b630a06411a97 ("cve-update-nvd2-native: new
CVE database fetcher") which is already in mickledore so would be a
candidate for backporting to walnascar and scarthgap.
> Also the directory changed to CVE_CHECK2 meanwhile, so Update it, too.
>
This changed in dd249921a5d6b8e472242b57415de3f210dc81f1
("cve-update-db-native: update structure") apparently, which is part of
walnascar so would be a candidate for backport to walnascar.
I think separate commits would be nice so we can backport the glob to
scarthgap too and have the CVE_CHECK2 backported to walnascar only.
Cheers,
Quentin
next prev parent reply other threads:[~2025-09-01 9:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-24 14:53 [PATCH] vulnerabilities: update nvdcve file name Peter Marko
2025-09-01 9:50 ` Quentin Schulz [this message]
2025-09-16 10:39 ` [docs] " Marko, Peter
2025-09-16 11:07 ` Antonin Godard
2025-10-11 21:37 ` Marko, Peter
2025-10-13 7:15 ` Antonin Godard
2025-09-17 14:13 ` Antonin Godard
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=44868213-2ff2-44bf-89a6-48e1dc6d3b80@cherry.de \
--to=quentin.schulz@cherry.de \
--cc=docs@lists.yoctoproject.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox