From: "srinuvasan.a via isar-users" <isar-users@googlegroups.com>
To: isar-users@googlegroups.com
Cc: christoph.steiger@siemens.com, felix.moessbauer@siemens.com,
cedric.hombourger@siemens.com, jan.kiszka@siemens.com,
srinuvasan <srinuvasan.a@siemens.com>
Subject: [PATCH 1/1] meta: derive ROOTFS_DISTRO correctly in sbom-chroot's do_prepare_rootfs
Date: Thu, 11 Sep 2025 18:34:08 +0530 [thread overview]
Message-ID: <20250911130408.3836054-2-srinuvasan.a@siemens.com> (raw)
In-Reply-To: <20250911130408.3836054-1-srinuvasan.a@siemens.com>
From: srinuvasan <srinuvasan.a@siemens.com>
In downstream layers, the ROOTFS_DISTRO may differ from "debian".
During `rootfs_prepare` of `sbom-chroot`, this causes failures such as:
| DEBUG: Executing shell function rootfs_prepare
| tar: .../debian-bookworm-amd64.tar.zst: Cannot open: No such file or directory
| tar: Error is not recoverable: exiting now
| WARNING: exit code 2 from a shell command.
The actual bootstrap archive generated was:
industrial-bookworm-amd64.tar.zst
Fix this by deriving ROOTFS_DISTRO from the current DISTRO, ensuring the
bootstrap tarball is unpacked and configured correctly.
As part of this change, remove `ROOTFS_DISTRO`, `ROOTFS_ARCH`, and
`ROOTFS_BASE_DISTRO` from the `sbom-chroot` recipe.
This modification brings it in line with the sbuild-chroot-target recipe.
Note: The sbom class is already inherited via rootfs, so it can be removed from the sbom-chroot recipe.
Signed-off-by: srinuvasan <srinuvasan.a@siemens.com>
---
meta/recipes-devtools/sbom-chroot/sbom-chroot.bb | 5 -----
1 file changed, 5 deletions(-)
diff --git a/meta/recipes-devtools/sbom-chroot/sbom-chroot.bb b/meta/recipes-devtools/sbom-chroot/sbom-chroot.bb
index 6f27f842..7f5ebc5b 100644
--- a/meta/recipes-devtools/sbom-chroot/sbom-chroot.bb
+++ b/meta/recipes-devtools/sbom-chroot/sbom-chroot.bb
@@ -8,11 +8,6 @@ LIC_FILES_CHKSUM = "file://${LAYERDIR_core}/licenses/COPYING.GPLv2;md5=751419260
PV = "1.0"
inherit rootfs
-inherit sbom
-
-ROOTFS_ARCH = "${HOST_ARCH}"
-ROOTFS_DISTRO = "${HOST_DISTRO}"
-ROOTFS_BASE_DISTRO = "${HOST_BASE_DISTRO}"
ROOTFS_FEATURES = "no-generate-initrd"
--
2.39.5
--
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/20250911130408.3836054-2-srinuvasan.a%40siemens.com.
next prev parent reply other threads:[~2025-09-11 13:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-11 13:04 [PATCH 0/1] Add SBOM generation with debsbom srinuvasan.a via isar-users
2025-09-11 13:04 ` srinuvasan.a via isar-users [this message]
2025-09-11 13:53 ` [PATCH 1/1] meta: derive ROOTFS_DISTRO correctly in sbom-chroot's do_prepare_rootfs 'MOESSBAUER, Felix' via isar-users
2025-09-12 8:17 ` [PATCH 0/1] Add SBOM generation with debsbom Srinuvasan Arjunan
2025-09-12 9:34 ` Srinuvasan Arjunan
2025-09-12 11:02 ` 'MOESSBAUER, Felix' 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=20250911130408.3836054-2-srinuvasan.a@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=srinuvasan.a@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