From: "'Felix Moessbauer' via isar-users" <isar-users@googlegroups.com>
To: isar-users@googlegroups.com
Cc: christoph.steiger@siemens.com,
Felix Moessbauer <felix.moessbauer@siemens.com>
Subject: [PATCH v4 0/2] Update debsbom tool
Date: Wed, 9 Sep 2026 08:18:29 +0200 [thread overview]
Message-ID: <20260909061831.1241330-1-felix.moessbauer@siemens.com> (raw)
Changes since v3:
- drop "imager sbom: simplify invocation of debsbom tool" patch:
to get correct directory permissions under schroot, we must
explicitly create the directory we deploy to
- p2: explicitly create the directory we deploy to
Changes since v2:
- delete leftover recipe for 0.10.1
Changes since v1:
- bump debsbom version to 0.10.2 (which fixes the issues
found on 0.10.1)
Felix Moessbauer (2):
debsbom: update to v0.10.2
rootfs sbom: directly use captured apt state without extraction
meta/classes/sbom.bbclass | 11 ++++-------
...on3-debsbom_0.8.1.bb => python3-debsbom_0.10.2.bb} | 2 +-
2 files changed, 5 insertions(+), 8 deletions(-)
rename meta/recipes-support/python3-debsbom/{python3-debsbom_0.8.1.bb => python3-debsbom_0.10.2.bb} (95%)
--
2.55.0
--
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/20260909061831.1241330-1-felix.moessbauer%40siemens.com.
next reply other threads:[~2026-09-09 6:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-09 6:18 'Felix Moessbauer' via isar-users [this message]
2026-09-09 6:18 ` [PATCH v4 1/2] debsbom: update to v0.10.2 'Felix Moessbauer' via isar-users
2026-09-09 6:18 ` [PATCH v4 2/2] rootfs sbom: directly use captured apt state without extraction 'Felix Moessbauer' via isar-users
2026-09-14 12:31 ` [PATCH v4 0/2] Update debsbom tool Zhihang Wei
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=20260909061831.1241330-1-felix.moessbauer@siemens.com \
--to=isar-users@googlegroups.com \
--cc=christoph.steiger@siemens.com \
--cc=felix.moessbauer@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