From: "Yoann Congal" <yoann.congal@smile.fr>
To: <benjamin.robin@bootlin.com>, <openembedded-core@lists.openembedded.org>
Cc: <ross.burton@arm.com>, <Peter.Marko@siemens.com>,
<olivier.benjamin@bootlin.com>,
<mathieu.dubois-briand@bootlin.com>,
<thomas.petazzoni@bootlin.com>
Subject: Re: [OE-core] [PATCH] python3-sbom-cve-check: update to version 1.3.5
Date: Mon, 14 Sep 2026 20:10:49 +0200 [thread overview]
Message-ID: <DLF8PKQZWT9D.QFDCJVVGNT03@smile.fr> (raw)
In-Reply-To: <20260914-sbom-cve-check-update-1-3-5-v1-1-5d2d69902368@bootlin.com>
On Mon Sep 14, 2026 at 6:49 PM CEST, Benjamin Robin via lists.openembedded.org wrote:
> For details on this new release, see:
> https://github.com/bootlin/sbom-cve-check/releases/tag/v1.3.5
>
> Signed-off-by: Benjamin Robin (Schneider Electric) <benjamin.robin@bootlin.com>
> ---
> ...{python3-sbom-cve-check_1.3.4.bb => python3-sbom-cve-check_1.3.5.bb} | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Hello,
Should I plan to upgrade to 1.3.5 on wrynose as well?
For reference, the changelog is:
| ## v1.3.5
|
| ### Added or Changed
|
| - Reduced peak memory usage while building database indexes.
| - Cached compiled-source path validation results to avoid repeated validation
| and duplicate warnings about missing important files in Linux kernel builds.
| - Added the `--rich-logging` command line option.
|
| ### Fixed
|
| - Prevented redundant database updates when multiple `sbom-cve-check`
| processes initialize the same database concurrently. Database initialization
| and indexing are now serialized across processes, allowing waiting processes
| to continue once initialization is complete, thereby substantially improving
| the parallel execution of multiple `sbom-cve-check` instances when a database
| update is needed.
Regards,
--
Yoann Congal
Smile ECS
next prev parent reply other threads:[~2026-09-14 18:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-14 16:49 [PATCH] python3-sbom-cve-check: update to version 1.3.5 Benjamin Robin (Schneider Electric)
2026-09-14 18:10 ` Yoann Congal [this message]
2026-09-14 18:47 ` [OE-core] " Marko, Peter
2026-09-15 7:50 ` Benjamin Robin
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=DLF8PKQZWT9D.QFDCJVVGNT03@smile.fr \
--to=yoann.congal@smile.fr \
--cc=Peter.Marko@siemens.com \
--cc=benjamin.robin@bootlin.com \
--cc=mathieu.dubois-briand@bootlin.com \
--cc=olivier.benjamin@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@arm.com \
--cc=thomas.petazzoni@bootlin.com \
/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