From: Joshua Watt <jpewhacker@gmail.com>
To: openembedded-core@lists.openembedded.org
Cc: Joshua Watt <JPEWhacker@gmail.com>
Subject: [OE-core][PATCH] lib: oe: cve_check: Mark variable flag dependencies
Date: Mon, 14 Apr 2025 09:47:44 -0600 [thread overview]
Message-ID: <20250414154744.1452161-1-JPEWhacker@gmail.com> (raw)
Marks CVE check functions which depend on non-constant variable flags as
depending on the variables. This allows changes in the flags to
correctly trigger a rebuild
Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
---
meta/lib/oe/cve_check.py | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta/lib/oe/cve_check.py b/meta/lib/oe/cve_check.py
index 5c272ba4ff3..5ace3cf5533 100644
--- a/meta/lib/oe/cve_check.py
+++ b/meta/lib/oe/cve_check.py
@@ -153,6 +153,7 @@ def parse_cves_from_patch_file(patch_file):
return cve_ids
+@bb.parse.vardeps("CVE_STATUS")
def get_patched_cves(d):
"""
Determines the CVE IDs that have been solved by either patches incuded within
@@ -289,6 +290,7 @@ def convert_cve_version(version):
return version + update
+@bb.parse.vardeps("CVE_STATUS", "CVE_CHECK_STATUSMAP")
def decode_cve_status(d, cve):
"""
Convert CVE_STATUS into status, vendor, product, detail and description.
--
2.49.0
reply other threads:[~2025-04-14 15:47 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=20250414154744.1452161-1-JPEWhacker@gmail.com \
--to=jpewhacker@gmail.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