From: Peter Marko Date: Wed, 7 Jun 2017 06:04:30 +0000 (+0200) Subject: cve-check: clean cve-check recipe result before re-building X-Git-Tag: uninative-1.7~580 X-Git-Url: https://code.ossystems.io/gitweb?a=commitdiff_plain;h=85b4941c71a0e3c08a8c48d52a94dfe2897d2c92;p=openembedded-core.git cve-check: clean cve-check recipe result before re-building If there is cve report for a recipe in previous build and there is no result for current one, old cves are kept in CVE_CHECK_DIR. This happens on version upgrade or when cve/recipe is whitelisted. Signed-off-by: Peter Marko Signed-off-by: Ross Burton --- diff --git a/meta/classes/cve-check.bbclass b/meta/classes/cve-check.bbclass index 3a9e227288..09487f1174 100644 --- a/meta/classes/cve-check.bbclass +++ b/meta/classes/cve-check.bbclass @@ -83,6 +83,11 @@ python cve_check_write_rootfs_manifest () { import shutil + if d.getVar("CVE_CHECK_COPY_FILES") == "1": + deploy_file = os.path.join(d.getVar("CVE_CHECK_DIR"), d.getVar("PN")) + if os.path.exists(deploy_file): + bb.utils.remove(deploy_file) + if os.path.exists(d.getVar("CVE_CHECK_TMP_FILE")): bb.note("Writing rootfs CVE manifest") deploy_dir = d.getVar("DEPLOY_DIR_IMAGE")