From: Anton Mikanovich <amikan@ilbers.de>
To: isar-users@googlegroups.com
Subject: Re: [PATCH] meta/recipes-devtools/sbom-chroot: drop initrd generation via ROOTFS_FEATURE:remove
Date: Mon, 5 Jan 2026 11:54:21 +0200 [thread overview]
Message-ID: <7811b49f-18ee-40ff-9500-b57309e40869@ilbers.de> (raw)
In-Reply-To: <20251223100341.4223-1-srinuvasan.a@siemens.com>
Applied to next, thanks.
23/12/2025 12:03, srinuvasan.a via isar-users wrote:
> From: srinuvasan <srinuvasan.a@siemens.com>
>
> Recent changes require disabling initrd generation using
> ROOTFS_FEATURE:remove = "generate-initrd" instead of
> ROOTFS_FEATURE = "no-generate-initrd".
>
> Update the recipe accordingly to align with the latest mechanism.
>
> Signed-off-by: srinuvasan <srinuvasan.a@siemens.com>
> ---
> meta/recipes-devtools/sbom-chroot/sbom-chroot.bb | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/recipes-devtools/sbom-chroot/sbom-chroot.bb b/meta/recipes-devtools/sbom-chroot/sbom-chroot.bb
> index 58200382..5cf43db8 100644
> --- a/meta/recipes-devtools/sbom-chroot/sbom-chroot.bb
> +++ b/meta/recipes-devtools/sbom-chroot/sbom-chroot.bb
> @@ -13,7 +13,7 @@ ROOTFS_ARCH = "${HOST_ARCH}"
> ROOTFS_DISTRO = "${@get_rootfs_distro(d)}"
> ROOTFS_BASE_DISTRO = "${HOST_BASE_DISTRO}"
>
> -ROOTFS_FEATURES = "no-generate-initrd"
> +ROOTFS_FEATURES:remove = "generate-initrd"
> ROOTFS_INSTALL_COMMAND:remove = "rootfs_restore_initrd_tooling"
>
> # additional packages for the SBOM chroot
--
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/7811b49f-18ee-40ff-9500-b57309e40869%40ilbers.de.
prev parent reply other threads:[~2026-01-05 9:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-23 10:03 srinuvasan.a via isar-users
2026-01-05 9:54 ` Anton Mikanovich [this message]
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=7811b49f-18ee-40ff-9500-b57309e40869@ilbers.de \
--to=amikan@ilbers.de \
--cc=isar-users@googlegroups.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