public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Alexander Kanavin <alex.kanavin@gmail.com>
To: openembedded-core@lists.openembedded.org
Cc: Alexander Kanavin <alex@linutronix.de>
Subject: [PATCH 2/2] sbom-cve-check: exclude recipes from version checks and version updates
Date: Wed, 22 Apr 2026 17:18:58 +0200	[thread overview]
Message-ID: <20260422151858.2598801-2-alex.kanavin@gmail.com> (raw)
In-Reply-To: <20260422151858.2598801-1-alex.kanavin@gmail.com>

From: Alexander Kanavin <alex@linutronix.de>

These recipes rely on AUTOREV enabled with a fragment, and upstream otherwise
updates them far too often to make regular version updates feasible.

Signed-off-by: Alexander Kanavin <alex@linutronix.de>
---
 .../recipes-devtools/sbom-cve-check/sbom-cve-check-update-db.inc | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/recipes-devtools/sbom-cve-check/sbom-cve-check-update-db.inc b/meta/recipes-devtools/sbom-cve-check/sbom-cve-check-update-db.inc
index fbdc561e8c..8f8639ab6c 100644
--- a/meta/recipes-devtools/sbom-cve-check/sbom-cve-check-update-db.inc
+++ b/meta/recipes-devtools/sbom-cve-check/sbom-cve-check-update-db.inc
@@ -2,6 +2,7 @@
 
 INHIBIT_DEFAULT_DEPS = "1"
 EXCLUDE_FROM_WORLD = "1"
+RECIPE_NO_UPDATE_REASON = "Recipe is enabled via fragment that also sets AUTOREV, and so it doesn't require manual updates"
 
 inherit native
 require conf/sbom-cve-check-config.inc
-- 
2.47.3



  reply	other threads:[~2026-04-22 15:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-22 15:18 [PATCH 1/2] libjpeg-turbo: exclude x.y.9z versions from upstream check Alexander Kanavin
2026-04-22 15:18 ` Alexander Kanavin [this message]
2026-04-23 14:22   ` [OE-core] [PATCH 2/2] sbom-cve-check: exclude recipes from version checks and version updates Ross Burton
2026-04-24 14:29     ` Alexander Kanavin

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=20260422151858.2598801-2-alex.kanavin@gmail.com \
    --to=alex.kanavin@gmail.com \
    --cc=alex@linutronix.de \
    --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