Re: [PATCH 0/2] Fix issue around missing initrd on partial rebuilds

["'Quirin Gylstorff' via isar-users" <isar-users@googlegroups.com>]

On 7/14/26 3:34 PM, Felix Moessbauer wrote:
> 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
> 

Looks good to me. ACK
Quirin
> 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(-)
> 

-- 
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/2655470b-5d1e-41a5-a3fe-74cbdf7d0e80%40siemens.com.