From: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH v2] uki.bbclass: fix building of UKI images with multiple initramfs fstypes
Date: Tue, 20 Jan 2026 04:43:13 +0200 [thread overview]
Message-ID: <20260120024313.3467088-1-dmitry.baryshkov@oss.qualcomm.com> (raw)
If INITRAMFS_FSTYPES contains more than one entry, ukify build command
will fail as INITRD_ARCHIVE will contain extra strings. Use only the
first initramfs type, letting the user to specify other fstypes in
INITRAMFS_FSTYPES.
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
---
meta/classes-recipe/uki.bbclass | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/meta/classes-recipe/uki.bbclass b/meta/classes-recipe/uki.bbclass
index a2b1c8a82d6f..ea449540db66 100644
--- a/meta/classes-recipe/uki.bbclass
+++ b/meta/classes-recipe/uki.bbclass
@@ -73,8 +73,6 @@ require ../conf/image-uefi.conf
INITRAMFS_IMAGE ?= "core-image-minimal-initramfs"
-INITRD_ARCHIVE ?= "${INITRAMFS_IMAGE}-${MACHINE}.${INITRAMFS_FSTYPES}"
-
do_image_complete[depends] += "${INITRAMFS_IMAGE}:do_image_complete"
UKIFY_CMD ?= "ukify build"
@@ -127,7 +125,8 @@ python do_uki() {
ukify_cmd += " --stub %s" % (stub)
# initrd
- initramfs_image = "%s" % (d.getVar('INITRD_ARCHIVE'))
+ uki_fstype = d.getVar("INITRAMFS_FSTYPES").split()[0]
+ initramfs_image = "%s-%s.%s" % (d.getVar('INITRAMFS_IMAGE'), d.getVar('MACHINE'), uki_fstype)
ukify_cmd += " --initrd=%s" % (os.path.join(deploy_dir_image, initramfs_image))
# kernel
--
2.47.3
next reply other threads:[~2026-01-20 2:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-20 2:43 Dmitry Baryshkov [this message]
2026-01-23 12:53 ` [OE-core] [PATCH v2] uki.bbclass: fix building of UKI images with multiple initramfs fstypes Paul Barker
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=20260120024313.3467088-1-dmitry.baryshkov@oss.qualcomm.com \
--to=dmitry.baryshkov@oss.qualcomm.com \
--cc=openembedded-core@lists.openembedded.org \
/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