summaryrefslogtreecommitdiffstats
path: root/documentation/ref-manual
diff options
context:
space:
mode:
authorMarta Rybczynska <rybczynska@gmail.com>2025-02-18 16:55:29 +0100
committerRichard Purdie <richard.purdie@linuxfoundation.org>2025-02-26 14:49:27 +0000
commit8bb220aa1112f93af0a8b6577f34e095492baa52 (patch)
tree1eb31bba181acf8a42894f26481162dd408797db /documentation/ref-manual
parentb3347ef7269c55c5750ca21b87396af4a0cf2644 (diff)
downloadpoky-8bb220aa1112f93af0a8b6577f34e095492baa52.tar.gz
vulnerabilities/classes: remove references to cve-check text format
The text format has been removed, so also remove references and examples using this format. Replace with examples with the JSON format. (From yocto-docs rev: a52cd7bcadccc53e982f90d6e170d00798322597) Signed-off-by: Marta Rybczynska <marta.rybczynska@ygreky.com> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/ref-manual')
-rw-r--r--documentation/ref-manual/classes.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/documentation/ref-manual/classes.rst b/documentation/ref-manual/classes.rst
index 8763e9e17e..b93279ff63 100644
--- a/documentation/ref-manual/classes.rst
+++ b/documentation/ref-manual/classes.rst
@@ -600,7 +600,7 @@ You can also look for vulnerabilities in specific packages by passing
600``-c cve_check`` to BitBake. 600``-c cve_check`` to BitBake.
601 601
602After building the software with Bitbake, CVE check output reports are available in ``tmp/deploy/cve`` 602After building the software with Bitbake, CVE check output reports are available in ``tmp/deploy/cve``
603and image specific summaries in ``tmp/deploy/images/*.cve`` or ``tmp/deploy/images/*.json`` files. 603and image specific summaries in ``tmp/deploy/images/*.json`` files.
604 604
605When building, the CVE checker will emit build time warnings for any detected 605When building, the CVE checker will emit build time warnings for any detected
606issues which are in the state ``Unpatched``, meaning that CVE issue seems to affect the software component 606issues which are in the state ``Unpatched``, meaning that CVE issue seems to affect the software component