Olaf Hering composed on 2018-03-15 16:48 (UTC+0100):
The current mindset is that mkinitrd must be run unconditionally when a kernel or kmp is installed, contrary to all other pkgs, they use %posttrans to update> either bootloader or initrd just once at the very end of the transaction.
To compensate for that mindset, the minimal version of a workaround looks like that: # touch /.buildenv # zypper dup # test -e /boot/initrd || mkinitrd -B
How (approximately - I'm an MC adherent) I constrain initrd creation: # zypper al kernel-default # zypper up # zypper -v dup # zypper in kernel-default # rm /boot/do_purge_kernels # reboot # chattr +i /boot/initrd-<version-latest> -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org