From: Zhihang Wei <wzh@ilbers.de>
To: Felix Moessbauer <felix.moessbauer@siemens.com>,
isar-users@googlegroups.com
Cc: christoph.steiger@siemens.com
Subject: Re: [PATCH 0/6] Rework SBOM generation
Date: Tue, 28 Jul 2026 17:28:15 +0200 [thread overview]
Message-ID: <54cb22e2-d300-4dd4-92e8-551652b849f4@ilbers.de> (raw)
In-Reply-To: <20260720081347.3835974-1-felix.moessbauer@siemens.com>
Applied to next, thanks.
Zhihang
On 7/20/26 10:13, 'Felix Moessbauer' via isar-users wrote:
> The SBOM generation currently fails to capture the package checksums
> in case of partial rebuilds. This is because the apt-state is not
> captured before the rootfs cleanup.
>
> We fix this by capturing the apt-state (and copyright data) while it
> still is available. Then, we run the SBOM generator against that data
> in a dedicated task. By that, the SBOM generation also can be cached,
> if the rootfs does not change - speeding up the build on repeated runs.
>
> We further fix a SBOM chroot deploy race on multi-config builds.
>
> Best regards,
> Felix Moessbauer
>
> Felix Moessbauer (6):
> rootfs: capture apt-state before rootfs cleanup
> sbom: run generator as task with apt-cache as input
> wic: make dependency to sbom chroot explicit
> sbom: deploy sbom chroot to distro specific file
> sbom: align deploy dir names
> sbom: cache artifact in sstate cache
>
> meta/classes-recipe/imagetypes_wic.bbclass | 1 +
> meta/classes-recipe/rootfs.bbclass | 27 +++++++++++++---
> meta/classes/sbom.bbclass | 37 ++++++++++++++++------
> 3 files changed, 51 insertions(+), 14 deletions(-)
>
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/54cb22e2-d300-4dd4-92e8-551652b849f4%40ilbers.de.
prev parent reply other threads:[~2026-07-28 15:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-20 8:13 'Felix Moessbauer' via isar-users
2026-07-20 8:13 ` [PATCH 1/6] rootfs: capture apt-state before rootfs cleanup 'Felix Moessbauer' via isar-users
2026-07-20 8:13 ` [PATCH 2/6] sbom: run generator as task with apt-cache as input 'Felix Moessbauer' via isar-users
2026-07-20 8:13 ` [PATCH 3/6] wic: make dependency to sbom chroot explicit 'Felix Moessbauer' via isar-users
2026-07-20 8:13 ` [PATCH 4/6] sbom: deploy sbom chroot to distro specific file 'Felix Moessbauer' via isar-users
2026-07-20 8:13 ` [PATCH 5/6] sbom: align deploy dir names 'Felix Moessbauer' via isar-users
2026-07-20 8:13 ` [PATCH 6/6] sbom: cache artifact in sstate cache 'Felix Moessbauer' via isar-users
2026-07-28 15:28 ` Zhihang Wei [this message]
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=54cb22e2-d300-4dd4-92e8-551652b849f4@ilbers.de \
--to=wzh@ilbers.de \
--cc=christoph.steiger@siemens.com \
--cc=felix.moessbauer@siemens.com \
--cc=isar-users@googlegroups.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