[PATCH v4 0/2] Update debsbom tool

[PATCH v4 0/2] Update debsbom tool

['Felix Moessbauer' via isar-users]

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.

[PATCH v4 1/2] debsbom: update to v0.10.2

['Felix Moessbauer' via isar-users]

This brings a couple of bugfixes, as well as support to read the package
data from a tar file.

Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
---
 .../{python3-debsbom_0.8.1.bb => python3-debsbom_0.10.2.bb}     | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-support/python3-debsbom/{python3-debsbom_0.8.1.bb => python3-debsbom_0.10.2.bb} (95%)

diff --git a/meta/recipes-support/python3-debsbom/python3-debsbom_0.8.1.bb b/meta/recipes-support/python3-debsbom/python3-debsbom_0.10.2.bb
similarity index 95%
rename from meta/recipes-support/python3-debsbom/python3-debsbom_0.8.1.bb
rename to meta/recipes-support/python3-debsbom/python3-debsbom_0.10.2.bb
index 7fc9a8eb..1aec1369 100644
--- a/meta/recipes-support/python3-debsbom/python3-debsbom_0.8.1.bb
+++ b/meta/recipes-support/python3-debsbom/python3-debsbom_0.10.2.bb
@@ -35,7 +35,7 @@ SRC_URI = "git://github.com/siemens/debsbom.git;protocol=https;branch=main; \
            file://rules \
            file://0001-Use-old-license-description-in-pyproject.toml.patch \
            "
-SRCREV = "a76d4e784f84e73b98d2bbeadd28c602a8c13708"
+SRCREV = "9b5a5d6be05f1207356223f88b3080bd72722b9f"
 
 do_prepare_build[cleandirs] += "${S}/debian"
 do_prepare_build() {
-- 
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-2-felix.moessbauer%40siemens.com.

[PATCH v4 2/2] rootfs sbom: directly use captured apt state without extraction

['Felix Moessbauer' via isar-users]

Since version 0.10 debsbom is capable of reading the apt state from a
tarball instead of an extracted rootfs. By that, we can remove the
manual extraction of the apt state and instead directly pass the tarball
to debsbom.

Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
---
 meta/classes/sbom.bbclass | 11 ++++-------
 1 file changed, 4 insertions(+), 7 deletions(-)

diff --git a/meta/classes/sbom.bbclass b/meta/classes/sbom.bbclass
index b2e8aff6..dad8e8f6 100644
--- a/meta/classes/sbom.bbclass
+++ b/meta/classes/sbom.bbclass
@@ -51,20 +51,17 @@ EOF
 }
 
 generate_sbom() {
-    run_privileged_heredoc <<'EOF'
-        mkdir -p ${SBOM_CHROOT_LOCAL}/mnt/rootfs \
-                 ${SBOM_CHROOT_LOCAL}/mnt/deploy-dir
-        tar -xf ${WORKDIR}/${ROOTFS_APT_STATE} --zstd \
-            -C ${SBOM_CHROOT_LOCAL}/mnt/rootfs
-EOF
+    run_privileged \
+        mkdir -p ${SBOM_CHROOT_LOCAL}/mnt/deploy-dir
 
     TIMESTAMP=$(date --iso-8601=s -d @${SOURCE_DATE_EPOCH})
+    unzstd < ${WORKDIR}/${ROOTFS_APT_STATE} | \
     bwrap \
         --unshare-user \
         --unshare-pid \
         --bind ${SBOM_CHROOT_LOCAL} / \
         --bind ${SBOM_LOCAL_DEPLOYDIR} /mnt/deploy-dir \
-        -- debsbom -v generate ${SBOM_DEBSBOM_TYPE_ARGS} -r /mnt/rootfs -o /mnt/deploy-dir/'${ROOTFS_PACKAGE_SUFFIX}' \
+        -- debsbom -v generate ${SBOM_DEBSBOM_TYPE_ARGS} -r - -o /mnt/deploy-dir/'${ROOTFS_PACKAGE_SUFFIX}' \
             --distro-name '${SBOM_DISTRO_NAME}' --distro-supplier '${SBOM_DISTRO_SUPPLIER}' \
             --distro-version '${SBOM_DISTRO_VERSION}' --distro-arch '${DISTRO_ARCH}' \
             --base-distro-vendor '${SBOM_BASE_DISTRO_VENDOR}' \
-- 
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-3-felix.moessbauer%40siemens.com.

Re: [PATCH v4 0/2] Update debsbom tool

[Zhihang Wei]

Applied to next, thanks.

Zhihang

On 9/9/26 08:18, 'Felix Moessbauer' via isar-users wrote:
> 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%)
>

-- 
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/ade8b263-3145-4c5d-8121-ee9b2d56e91e%40ilbers.de.