public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "vboudevin" <valentin.boudevin@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v6 2/4] cvelistv5: add a new recipe
Date: Mon, 02 Feb 2026 05:48:51 -0800	[thread overview]
Message-ID: <442096.1770040131832557569@lists.openembedded.org> (raw)
In-Reply-To: <49de779cc2db0ef5c2bade9c8b07e076dedc340f.camel@linuxfoundation.org>

[-- Attachment #1: Type: text/plain, Size: 443 bytes --]

I wanted to indicate that the recipe is not meant to be used with a fixed commit with a deterministic approach.

Having ${AUTOREV} by default can lead to many offline issues.

I guess the correct implementation would be to specify, in the documentation, the need for "SRCREV:pn-cvelistv5-native = "${AUTOREV}"" to stay up-to-date with CVE data, and also add this information in a comment inside the recipe.

Thank you for your feedback

[-- Attachment #2: Type: text/html, Size: 508 bytes --]

  reply	other threads:[~2026-02-02 13:48 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <188AFCD98EA3E578.3200434@lists.openembedded.org>
2026-01-16 19:05 ` [PATCH 1/1] improve_kerne_cve_report: Add a bbclass support ValentinBoudevin
2026-01-16 19:05   ` [PATCH v5 0/4] generate-cve-exclusions: Add a .bbclass ValentinBoudevin
2026-01-19 10:44     ` Daniel Turull
2026-01-16 19:05   ` [PATCH v5 1/4] generate-cve-exclusions: Add --output-json option ValentinBoudevin
2026-01-16 19:05   ` [PATCH v5 2/4] generate-cve-exclusions: Add a .bbclass ValentinBoudevin
2026-01-17 13:36     ` [OE-core] " Peter Kjellerstedt
2026-01-19 10:40       ` Daniel Turull
2026-01-16 19:05   ` [PATCH v5 3/4] generate-cve-exclusions: Move python script ValentinBoudevin
2026-01-16 19:05   ` [PATCH v5 4/4] linux: Add inherit on generate-cve-exclusions ValentinBoudevin
2026-01-17 13:38     ` [OE-core] " Peter Kjellerstedt
2026-01-19  9:35   ` [PATCH 1/1] improve_kerne_cve_report: Add a bbclass support Daniel Turull
2026-01-29 21:10 ` [PATCH v6 0/4] generate-cve-exclusions: Add a .bbclass ValentinBoudevin
2026-01-29 21:10   ` [PATCH v6 1/4] generate-cve-exclusions: Add output format option ValentinBoudevin
2026-01-29 21:10   ` [PATCH v6 2/4] cvelistv5: add a new recipe ValentinBoudevin
2026-02-01 11:56     ` [OE-core] " Mathieu Dubois-Briand
2026-02-01 15:12     ` Richard Purdie
2026-02-02 13:48       ` vboudevin [this message]
2026-02-02 14:04         ` Marta Rybczynska
2026-02-02 19:54           ` vboudevin
2026-01-29 21:10   ` [PATCH v6 3/4] kernel-generate-cve-exclusions: Add a .bbclass ValentinBoudevin
2026-01-29 21:10   ` [PATCH v6 4/4] generate-cve-exclusions: Move python script ValentinBoudevin

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=442096.1770040131832557569@lists.openembedded.org \
    --to=valentin.boudevin@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