From: "Devansh Patel -X (devanshp - E INFOCHIPS PRIVATE LIMITED at Cisco)" <devanshp@cisco.com>
To: openembedded-devel@lists.openembedded.org
Cc: xe-linux-external@cisco.com
Subject: [meta-virtualization][PATCH] go-logrus: correct CVE_PRODUCT mapping
Date: Thu, 20 Aug 2026 02:37:53 -0700 [thread overview]
Message-ID: <20260820093753.43396-1-devanshp@cisco.com> (raw)
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
reply other threads:[~2026-08-20 9:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260820093753.43396-1-devanshp@cisco.com \
--to=devanshp@cisco.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=xe-linux-external@cisco.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.