![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
https://bugzilla.suse.com/show_bug.cgi?id=1224773 https://bugzilla.suse.com/show_bug.cgi?id=1224773#c31 Ignaz Forster <iforster@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aplanas@suse.com Flags|needinfo?(iforster@suse.com |needinfo?(aplanas@suse.com) |) | --- Comment #31 from Ignaz Forster <iforster@suse.com> --- (In reply to Stefan Dirsch from comment #29)
2. transactional-update initrd doesn't work together with systemd-boot
Correct, currently systemd-boot is not directly integrated into transactional-update itself yet (i.e. the commands "initrd", "bootloader" and "grub.cfg" don't do the right thing on a systemd-boot system). systemd-boot support is generically implemented as a snapper plugin using the "sdbootutil" instead, because of course you can also use systemd-boot on non-transactional systems. The sdbootutil script also includes detection whether it is necessary to regenerate the initrd. @Alberto: On a first glance I couldn't find any RPM macro integration so that a RPM package calling %regenerate_initrd_post would trigger the initrd rebuild on a systemd-boot system. Am I missing something, or do we still have to implement this?
1. transactional-update initrd is not being executed when installing a KMP
See answer above - this is something which needs to be implemented on a RPM macro level... -- You are receiving this mail because: You are on the CC list for the bug.