From: "'MOESSBAUER, Felix' via isar-users" <isar-users@googlegroups.com>
To: "isar-users@googlegroups.com" <isar-users@googlegroups.com>,
"Bouska, Zdenek" <zdenek.bouska@siemens.com>
Cc: "Steiger, Christoph" <christoph.steiger@siemens.com>,
"Gylstorff, Quirin" <quirin.gylstorff@siemens.com>,
"Hombourger, Cedric" <cedric.hombourger@siemens.com>,
"Kiszka, Jan" <jan.kiszka@siemens.com>
Subject: Re: [PATCH v6 00/10] Add SBOM generation with debsbom
Date: Wed, 7 Jan 2026 15:06:34 +0000 [thread overview]
Message-ID: <90623bf31851d17dfe746459fbfae86461f59b9d.camel@siemens.com> (raw)
In-Reply-To: <AS1PR10MB5675B5F1D4273515A9E3F4A9EBA7A@AS1PR10MB5675.EURPRD10.PROD.OUTLOOK.COM>
On Fri, 2025-12-05 at 15:08 +0000, Bouška, Zdeněk (FT D EU CZ PDS1 ICC
1) wrote:
> > This patchset adds proper SBOM generation in the two standard formats
> > SPDX and CycloneDX during the rootfs generation process.
>
> libre2-11 (provider of virtual package libre2-11-absl20240722) is
> missing as dependency of libgrpc29t64 in
> build/tmp/deploy/images/qemuamd64/isar-image-base-debian-trixie-qemuamd64.wic.cdx.json
> See dependencies on Debian Trixie [1].
Thanks for the reproducer. This is indeed a debsbom bug, but only
affects the mapping of dependencies. The provider package is still
added to the flat list of packages in the SBOM (under the actual name,
not the virtual one).
I created and upstream issue for tracking:
https://github.com/siemens/debsbom/issues/164
Best regards,
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/90623bf31851d17dfe746459fbfae86461f59b9d.camel%40siemens.com.
next prev parent reply other threads:[~2026-01-07 15:06 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-01 8:58 'Felix Moessbauer' via isar-users
2025-12-01 8:58 ` [PATCH v6 01/10] refactor: move get_rootfs_distro from sdk into rootfs 'Felix Moessbauer' via isar-users
2025-12-01 8:58 ` [PATCH v6 02/10] meta: package python libraries for SBOM generation 'Felix Moessbauer' via isar-users
2025-12-01 8:58 ` [PATCH v6 03/10] meta: package python3-debsbom 'Felix Moessbauer' via isar-users
2025-12-01 8:58 ` [PATCH v6 04/10] meta: add SBOM generation with debsbom 'Felix Moessbauer' via isar-users
2025-12-01 8:58 ` [PATCH v6 05/10] override distro vendor in SBOM on Ubuntu 'Felix Moessbauer' via isar-users
2025-12-01 8:58 ` [PATCH v6 06/10] add support to add imager dependencies to BOM 'Felix Moessbauer' via isar-users
2025-12-01 8:58 ` [PATCH v6 07/10] wic: create uniform manifest describing all image components 'Felix Moessbauer' via isar-users
2025-12-01 8:58 ` [PATCH v6 08/10] qemuamd64: add IMAGER_BOM entries 'Felix Moessbauer' via isar-users
2025-12-01 8:58 ` [PATCH v6 09/10] imager: create SBOM of IMAGER_BOM packages 'Felix Moessbauer' via isar-users
2025-12-01 8:58 ` [PATCH v6 10/10] wic: create uniform SBOM describing all image components 'Felix Moessbauer' via isar-users
2025-12-01 9:15 ` [PATCH v6 00/10] Add SBOM generation with debsbom 'Jan Kiszka' via isar-users
2025-12-03 13:32 ` 'MOESSBAUER, Felix' via isar-users
2025-12-05 15:08 ` 'Bouska, Zdenek' via isar-users
2026-01-07 15:06 ` 'MOESSBAUER, Felix' via isar-users [this message]
2026-01-12 10:08 ` 'MOESSBAUER, Felix' via isar-users
2026-01-14 8:51 ` 'Bouska, Zdenek' via isar-users
2025-12-09 14:21 ` Zhihang Wei
2025-12-09 14:49 ` 'MOESSBAUER, Felix' via isar-users
2025-12-09 14:56 ` Zhihang Wei
2025-12-11 9:15 ` Zhihang Wei
2025-12-12 10:24 ` 'Jan Kiszka' via isar-users
2025-12-15 7:35 ` 'MOESSBAUER, Felix' via isar-users
2025-12-17 15:22 ` 'Jan Kiszka' via isar-users
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=90623bf31851d17dfe746459fbfae86461f59b9d.camel@siemens.com \
--to=isar-users@googlegroups.com \
--cc=cedric.hombourger@siemens.com \
--cc=christoph.steiger@siemens.com \
--cc=felix.moessbauer@siemens.com \
--cc=jan.kiszka@siemens.com \
--cc=quirin.gylstorff@siemens.com \
--cc=zdenek.bouska@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