From: "Devansh Patel" <devanshp@cisco.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-virtualization][PATCH] go-logrus: correct CVE_PRODUCT mapping
Date: Thu, 20 Aug 2026 22:03:11 -0700 [thread overview]
Message-ID: <2326395.1787288591759544747@lists.openembedded.org> (raw)
In-Reply-To: <20260820093753.43396-1-devanshp@cisco.com>
[-- Attachment #1: Type: text/plain, Size: 1159 bytes --]
On Thu, Aug 20, 2026 at 03:07 PM, Devansh Patel wrote:
>
> From: Devansh Patel <devanshp@cisco.com>
>
> The default "go-logrus" product does not match the packaged Logrus
> identity in NVD, so its CVE records are not associated with the recipe.
>
> Use "turbopuffer:logrus", the exact NVD identity for the
> github.com/sirupsen/logrus source.
>
> Signed-off-by: Devansh Patel <devanshp@cisco.com>
> ---
> recipes-devtools/go/go-logrus_git.bb | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/recipes-devtools/go/go-logrus_git.bb
> b/recipes-devtools/go/go-logrus_git.bb
> index 7b9e31a5..4f8a255e 100644
> --- a/recipes-devtools/go/go-logrus_git.bb
> +++ b/recipes-devtools/go/go-logrus_git.bb
> @@ -12,6 +12,8 @@ SRC_URI =
> "git://${PKG_NAME};branch=master;protocol=https"
> SRCREV = "a29884b9be3dc22c18338c0fe5a51d23e69731e4"
> PV = "1.9.4+git"
>
> +CVE_PRODUCT = "turbopuffer:logrus"
> +
> inherit meta-virt-depreciated-warning
>
> do_install() {
> --
> 2.35.6
Hi,
Please ignore this patch, as it was mistakenly submitted to the wrong layer mailing list. Apologies for the mix-up!
Regards,
Devansh
[-- Attachment #2: Type: text/html, Size: 1278 bytes --]
prev parent reply other threads:[~2026-08-21 5:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-20 9:37 [meta-virtualization][PATCH] go-logrus: correct CVE_PRODUCT mapping Devansh Patel -X (devanshp - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-08-21 5:03 ` Devansh Patel [this message]
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=2326395.1787288591759544747@lists.openembedded.org \
--to=devanshp@cisco.com \
--cc=openembedded-devel@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