public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "'Jan Kiszka' via isar-users" <isar-users@googlegroups.com>
To: isar-users <isar-users@googlegroups.com>
Cc: Cedric Hombourger <cedric.hombourger@siemens.com>,
	Zhihang Wei <wzh@ilbers.de>
Subject: [PATCH] rootfs: Restore previous naming scheme in INITRD_DEPLOY_FILE
Date: Sat, 29 Nov 2025 16:13:56 +0100	[thread overview]
Message-ID: <3a14d171-f4b9-40c3-929f-0e34e99d2d16@siemens.com> (raw)

From: Jan Kiszka <jan.kiszka@siemens.com>

Might have been accidentally changed, specifically as initramfs.bbclass
was not updated as well, and that broke downstream users of
INITRD_DEPLOY_FILE via wic.

Fixes: c3c4e72cbfc4 ("image: introduce IMAGE_INITRD, deprecate INITRD_IMAGE")
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
---
 meta/classes/image.bbclass | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/classes/image.bbclass b/meta/classes/image.bbclass
index b030024f..d367d8c7 100644
--- a/meta/classes/image.bbclass
+++ b/meta/classes/image.bbclass
@@ -29,7 +29,7 @@ INITRD_IMAGE ?= ""
 IMAGE_INITRD ?= ""
 
 # Name of the deployed initrd image
-INITRD_DEPLOY_FILE = "${@ d.getVar('IMAGE_INITRD') or '${PN}' }-${DISTRO}-${MACHINE}-initrd.img"
+INITRD_DEPLOY_FILE = "${@ d.getVar('IMAGE_INITRD') or '${PN}' }-${DISTRO}-${MACHINE}.initrd.img"
 
 # Make sure dependent initramfs recipe is built
 do_image[depends] += "${@ '${IMAGE_INITRD}:do_build' if '${IMAGE_INITRD}' else '' }"
-- 
2.51.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/3a14d171-f4b9-40c3-929f-0e34e99d2d16%40siemens.com.

             reply	other threads:[~2025-11-29 15:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-29 15:13 'Jan Kiszka' via isar-users [this message]
2025-12-03 11:52 ` 'Quirin Gylstorff' via isar-users
2025-12-03 14:38   ` 'Quirin Gylstorff' via isar-users
2025-12-09 10:15 ` Zhihang Wei
2025-12-11 13:53   ` 'Jan Kiszka' via isar-users
2025-12-11 16:09     ` Zhihang Wei
2025-12-11 16:39       ` 'Jan Kiszka' via isar-users
2025-12-12 10:29         ` 'Jan Kiszka' via isar-users
2025-12-12 14:36           ` Zhihang Wei
2025-12-12 14:37             ` 'Jan Kiszka' 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=3a14d171-f4b9-40c3-929f-0e34e99d2d16@siemens.com \
    --to=isar-users@googlegroups.com \
    --cc=cedric.hombourger@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