From: "'MOESSBAUER, Felix' via isar-users" <isar-users@googlegroups.com>
To: "Steiger, Christoph" <christoph.steiger@siemens.com>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Cc: "Kiszka, Jan" <jan.kiszka@siemens.com>,
"cedric.hombourger@siemens.com" <cedric.hombourger@siemens.com>,
"Hillier, Gernot" <gernot.hillier@siemens.com>
Subject: Re: [PATCH 3/3] meta: add SBOM generation with debsbom
Date: Thu, 11 Sep 2025 10:07:06 +0000 [thread overview]
Message-ID: <d034abf5e50e6125e8ba91d8e0b8f0c52979298e.camel@siemens.com> (raw)
In-Reply-To: <20250909080528.95765-4-christoph.steiger@siemens.com>
On Tue, 2025-09-09 at 10:05 +0200, Christoph Steiger wrote:
> Generate SBOMs for every rootfs that is created. These SBOMs are placed
> in the image deploy directory.
>
> For the generation a small chroot with debsbom installed is created and
> from that the rootfs of the image is scanned.
>
> The sbom generation is bound to the rootfs feature `generate-sbom`
> which is activated per default now.
>
> Signed-off-by: Christoph Steiger <christoph.steiger@siemens.com>
> Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
> ---
> meta/classes/image.bbclass | 2 +-
> meta/classes/rootfs.bbclass | 6 +-
> meta/classes/sbom.bbclass | 60 ++++++++++++++++++
> meta/classes/sdk.bbclass | 2 +-
> .../sbom-chroot/sbom-chroot.bb | 31 +++++++++
> .../files/debsbom-0.1.0.tar.gz | Bin 9383 -> 0 bytes
> ...sbom_0.1.0.bb => python3-debsbom_0.0.1.bb} | 2 +
Hi, you renamed that file between p2 and p3. That probably is not
intentional as well. Maybe you could send out a cleanup of this series
along with an update of the debsbom upstream ref?
Felix
--
Siemens AG
Linux Expert Center
Friedrich-Ludwig-Bauer-Str. 3
85748 Garching, Germany
--
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/d034abf5e50e6125e8ba91d8e0b8f0c52979298e.camel%40siemens.com.
prev parent reply other threads:[~2025-09-11 10:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-09 8:05 [PATCH 0/3] Add " 'Christoph Steiger' via isar-users
2025-09-09 8:05 ` [PATCH 1/3] meta: package python libraries for SBOM generation 'Christoph Steiger' via isar-users
2025-09-09 8:05 ` [PATCH 2/3] meta: package python3-debsbom 'Christoph Steiger' via isar-users
2025-09-09 8:19 ` 'Christoph Steiger' via isar-users
2025-09-09 8:05 ` [PATCH 3/3] meta: add SBOM generation with debsbom 'Christoph Steiger' via isar-users
2025-09-11 10:07 ` 'MOESSBAUER, Felix' via isar-users [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=d034abf5e50e6125e8ba91d8e0b8f0c52979298e.camel@siemens.com \
--to=isar-users@googlegroups.com \
--cc=cedric.hombourger@siemens.com \
--cc=christoph.steiger@siemens.com \
--cc=felix.moessbauer@siemens.com \
--cc=gernot.hillier@siemens.com \
--cc=jan.kiszka@siemens.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