All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel McGregor <danismostlikely@gmail.com>
To: openembedded-core@lists.openembedded.org
Cc: Daniel McGregor <daniel.mcgregor@vecima.com>
Subject: [PATCH v2] util-linux-libuuid: use util-linux's CVE_PRODUCT value
Date: Wed, 29 Jan 2025 10:26:10 -0600	[thread overview]
Message-ID: <20250129162610.35102-1-daniel.mcgregor@vecima.com> (raw)
In-Reply-To: <181F354F7FEC52AE.31881@lists.openembedded.org>

util-linux and util-linux-libuuid should use the same CVE_PRODUCT
since they're the same product. They're just split off for package
dependency reasons.  Prior to this patch the libuuid recipe gave the
wrong CVE_PRODUCT value, causing some CVE check tools to fail on it.

Signed-off-by: Daniel McGregor <daniel.mcgregor@vecima.com>
---
 meta/recipes-core/util-linux/util-linux.inc | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/meta/recipes-core/util-linux/util-linux.inc b/meta/recipes-core/util-linux/util-linux.inc
index 56162ab1479..580ff488e42 100644
--- a/meta/recipes-core/util-linux/util-linux.inc
+++ b/meta/recipes-core/util-linux/util-linux.inc
@@ -43,3 +43,5 @@ SRC_URI = "${KERNELORG_MIRROR}/linux/utils/util-linux/v${MAJOR_VERSION}/util-lin
            "
 
 SRC_URI[sha256sum] = "d78b37a66f5922d70edf3bdfb01a6b33d34ed3c3cafd6628203b2a2b67c8e8b3"
+
+CVE_PRODUCT = "util-linux"
-- 
2.47.0



       reply	other threads:[~2025-01-29 16:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <181F354F7FEC52AE.31881@lists.openembedded.org>
2025-01-29 16:26 ` Daniel McGregor [this message]
2025-01-29 16:29 ` [PATCH v3] util-linux-libuuid: use util-linux's CVE_PRODUCT value Dan McGregor
     [not found] ` <181F36C8D7A37026.21193@lists.openembedded.org>
2025-01-30 20:27   ` [OE-core] " Dan McGregor

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=20250129162610.35102-1-daniel.mcgregor@vecima.com \
    --to=danismostlikely@gmail.com \
    --cc=daniel.mcgregor@vecima.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 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.