From: "'Felix Moessbauer' via isar-users" <isar-users@googlegroups.com>
To: isar-users@googlegroups.com
Cc: jan.kiszka@siemens.com, wzh@ilbers.de,
Felix Moessbauer <felix.moessbauer@siemens.com>
Subject: [PATCH v2 0/2] Make SBOM naming more robust against downstream changes
Date: Tue, 31 Mar 2026 09:38:54 +0200 [thread overview]
Message-ID: <20260331073856.1281781-1-felix.moessbauer@siemens.com> (raw)
The related inconsistencies have been found on isar-cip-core tests
(kas-cip.yml:kas/board/x86-uefi.yml:kas/opt/rt.yml:kas/opt/test.yml:kas/opt/trixie.yml)
where the IMAGE_FULLNAME variable is changed and no longer equal to
ROOTFS_PACKAGE_SUFFIX. Without the patches, the respective CIP variant cannot be built.
This patch should go into the v1.0 release, as it is critical for isar-cip-core
(rc-1 fails on CIP).
Changes since v1:
- rebased onto next
- adjusted test case to new (consistent) naming
- no code changes
Best regards,
Felix
Felix Moessbauer (2):
sbom: derive rootfs sbom name from ROOTFS_PACKAGE_SUFFIX
sbom: use ROOTFS_PACKAGE_SUFFIX on merging
meta/classes-recipe/imagetypes_wic.bbclass | 2 +-
meta/classes/sbom.bbclass | 2 +-
testsuite/cibase.py | 6 +++---
3 files changed, 5 insertions(+), 5 deletions(-)
--
2.53.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/20260331073856.1281781-1-felix.moessbauer%40siemens.com.
next reply other threads:[~2026-03-31 7:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-31 7:38 'Felix Moessbauer' via isar-users [this message]
2026-03-31 7:38 ` [PATCH v2 1/2] sbom: derive rootfs sbom name from ROOTFS_PACKAGE_SUFFIX 'Felix Moessbauer' via isar-users
2026-03-31 7:38 ` [PATCH v2 2/2] sbom: use ROOTFS_PACKAGE_SUFFIX on merging 'Felix Moessbauer' via isar-users
2026-03-31 7:40 ` [PATCH v2 0/2] Make SBOM naming more robust against downstream changes Zhihang Wei
2026-04-01 8:00 ` Zhihang Wei
2026-04-01 15:43 ` 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=20260331073856.1281781-1-felix.moessbauer@siemens.com \
--to=isar-users@googlegroups.com \
--cc=felix.moessbauer@siemens.com \
--cc=jan.kiszka@siemens.com \
--cc=wzh@ilbers.de \
/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