public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "'Felix Moessbauer' via isar-users" <isar-users@googlegroups.com>
To: isar-users@googlegroups.com
Cc: quirin.gylstorff@siemens.com,
	Felix Moessbauer <felix.moessbauer@siemens.com>
Subject: [PATCH 0/2] Fix issue around missing initrd on partial rebuilds
Date: Tue, 14 Jul 2026 15:34:20 +0200	[thread overview]
Message-ID: <20260714133422.1792603-1-felix.moessbauer@siemens.com> (raw)

When working with a in-tree initrd, the generation of the initrd has the
side effect of placing the initrd in /boot as well (in addition to the
deployment to the deploy dir). This part is currently skipped in case
the initrd is taken from the sstate cache, leading to reproducibility
issues of non-wic images (e.g. a rootfs tarball).

While this is just a reproducibility issue on wic images (as the initrd
is anyways replaced by the one from the deploy dir), it is a bug that
breaks booting on non-wic images.

Best regards,
Felix

Felix Moessbauer (2):
  rootfs: make DEPLOYDIR available to all rootfs
  fix(rootfs): generate in-tree initrd as part of image install

 meta/classes-recipe/image.bbclass     |  3 +--
 meta/classes-recipe/initramfs.bbclass | 39 ++++++++++++++++++++++++++-
 meta/classes-recipe/rootfs.bbclass    | 35 +++++-------------------
 3 files changed, 46 insertions(+), 31 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/20260714133422.1792603-1-felix.moessbauer%40siemens.com.

             reply	other threads:[~2026-07-14 13:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-14 13:34 'Felix Moessbauer' via isar-users [this message]
2026-07-14 13:34 ` [PATCH 1/2] rootfs: make DEPLOYDIR available to all rootfs 'Felix Moessbauer' via isar-users
2026-07-14 13:34 ` [PATCH 2/2] fix(rootfs): generate in-tree initrd as part of image install 'Felix Moessbauer' via isar-users
2026-07-17 14:40   ` 'MOESSBAUER, Felix' via isar-users
2026-07-17 14:42     ` Zhihang Wei
2026-07-14 14:32 ` [PATCH 0/2] Fix issue around missing initrd on partial rebuilds 'Quirin Gylstorff' via isar-users
2026-07-17 14:07 ` 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=20260714133422.1792603-1-felix.moessbauer@siemens.com \
    --to=isar-users@googlegroups.com \
    --cc=felix.moessbauer@siemens.com \
    --cc=quirin.gylstorff@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