From: "Davide Gardenal" <davidegarde2000@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: cve-check: building world doesn't create the manifest
Date: Fri, 29 Apr 2022 01:22:40 -0700 [thread overview]
Message-ID: <7kxD.1651220560041636184.iS66@lists.openembedded.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 799 bytes --]
Greetings,
In the current version of cve-check there is no way of creating the manifest when building world. The reason why is due to these two lines:
>
>
> ROOTFS_POSTPROCESS_COMMAND:prepend = "${@'cve_check_write_rootfs_manifest;
> ' if d.getVar('CVE_CHECK_CREATE_MANIFEST') == '1' else ''}"
> do_rootfs[recrdeptask] += "${@'do_cve_check' if
> d.getVar('CVE_CHECK_CREATE_MANIFEST') == '1' else ''}"
The problem is that in world there is no do_rootfs so the function cve_check_write_rootfs_manifest is never executed hence the manifest is not created.
My idea was to convert cve_check_write_rootfs_manifest to a handler listening for BuildCompleted but then if someone builds more than one image the output is broken.
Any suggestions are welcome and appreciated, thanks!
Davide
[-- Attachment #2: Type: text/html, Size: 832 bytes --]
next reply other threads:[~2022-04-29 8:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-29 8:22 Davide Gardenal [this message]
2022-04-29 15:39 ` [OE-core] cve-check: building world doesn't create the manifest Ralph Siemsen
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=7kxD.1651220560041636184.iS66@lists.openembedded.org \
--to=davidegarde2000@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