Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Benjamin Robin (Schneider Electric)" <benjamin.robin@bootlin.com>
To: openembedded-core@lists.openembedded.org
Cc: "Benjamin Robin (Schneider Electric)"
	<benjamin.robin@bootlin.com>,
	thomas.petazzoni@bootlin.com, mathieu.dubois-briand@bootlin.com,
	miquel.raynal@bootlin.com, antonin.godard@bootlin.com,
	kamel.bouhara@bootlin.com, pascal.eberhard@se.com,
	jpewhacker@gmail.com, Peter Marko <peter.marko@siemens.com>,
	Richard Purdie <richard.purdie@linuxfoundation.org>
Subject: [scarthgap v2 5/5] vex: fix rootfs manifest
Date: Fri, 21 Nov 2025 10:54:13 +0100	[thread overview]
Message-ID: <20251121095415.288301-6-benjamin.robin@bootlin.com> (raw)
In-Reply-To: <20251121095415.288301-1-benjamin.robin@bootlin.com>

Rootfs VEX file is created by gathering files from CVE_CHECK_DIR
(deploy directory), however recipes generate the files only in
CVE_CHECK_DIR (log directory).
This make the rootfs VEX be always empty without any message.

The code is copied from cve_check class, which writes to both, so let
keep them aligned and make also vex write both files.

Also add a warning for case that a cve file would be still missing.

Signed-off-by: Peter Marko <peter.marko@siemens.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
(cherry picked from commit ee6541d0940c65685aaafd7d41a59a9406392e7d)
Signed-off-by: Benjamin Robin (Schneider Electric) <benjamin.robin@bootlin.com>
---
 meta/classes/vex.bbclass | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/meta/classes/vex.bbclass b/meta/classes/vex.bbclass
index c447b37db89b..707e6f45a19a 100644
--- a/meta/classes/vex.bbclass
+++ b/meta/classes/vex.bbclass
@@ -213,6 +213,8 @@ python vex_write_rootfs_manifest () {
             with open(pkgfilepath) as j:
                 data = json.load(j)
                 cve_check_merge_jsons(json_data, data)
+        else:
+            bb.warn("Missing cve file for %s" % pkg)
 
     d.setVar("PN", save_pn)
 
@@ -306,9 +308,12 @@ def cve_write_data_json(d, cve_data, cve_status):
     cvelogpath = d.getVar("CVE_CHECK_SUMMARY_DIR")
     index_path = d.getVar("CVE_CHECK_SUMMARY_INDEX_PATH")
     bb.utils.mkdirhier(cvelogpath)
+    bb.utils.mkdirhier(os.path.dirname(deploy_file))
     fragment_file = os.path.basename(deploy_file)
     fragment_path = os.path.join(cvelogpath, fragment_file)
     with open(fragment_path, "w") as f:
         f.write(write_string)
+    with open(deploy_file, "w") as f:
+        f.write(write_string)
     with open(index_path, "a+") as f:
         f.write("%s\n" % fragment_path)
-- 
2.51.2



  parent reply	other threads:[~2025-11-21  9:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-21  9:54 [scarthgap v2 0/5] backport: allow to extract all CVE_STATUS info Benjamin Robin (Schneider Electric)
2025-11-21  9:54 ` [scarthgap v2 1/5] spdx30: provide all CVE_STATUS, not only Patched status Benjamin Robin (Schneider Electric)
2025-11-21  9:54 ` [scarthgap v2 2/5] vex.bbclass: add a new class Benjamin Robin (Schneider Electric)
2025-11-21  9:54 ` [scarthgap v2 3/5] cve-check: extract extending CVE_STATUS to library function Benjamin Robin (Schneider Electric)
2025-11-21  9:54 ` [scarthgap v2 4/5] spdx: extend CVE_STATUS variables Benjamin Robin (Schneider Electric)
2025-11-21  9:54 ` Benjamin Robin (Schneider Electric) [this message]
2025-11-21 10:35 ` [OE-core] [scarthgap v2 0/5] backport: allow to extract all CVE_STATUS info Marta Rybczynska
2025-11-21 10:42   ` Benjamin ROBIN

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=20251121095415.288301-6-benjamin.robin@bootlin.com \
    --to=benjamin.robin@bootlin.com \
    --cc=antonin.godard@bootlin.com \
    --cc=jpewhacker@gmail.com \
    --cc=kamel.bouhara@bootlin.com \
    --cc=mathieu.dubois-briand@bootlin.com \
    --cc=miquel.raynal@bootlin.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=pascal.eberhard@se.com \
    --cc=peter.marko@siemens.com \
    --cc=richard.purdie@linuxfoundation.org \
    --cc=thomas.petazzoni@bootlin.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