https://bugzilla.suse.com/show_bug.cgi?id=1226122 https://bugzilla.suse.com/show_bug.cgi?id=1226122#c36 Martin Wilck <martin.wilck@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS CC| |aplanas@suse.com --- Comment #36 from Martin Wilck <martin.wilck@suse.com> --- There's a pending PR to integrate sdbootutil-rpm-scriptlets back into suse-module-tools (https://github.com/openSUSE/suse-module-tools/pull/103). I believe that PR would have prevented the issue, at least if sdbootutil was not in the set of packages to install. It might cause other issues, though. Adding Alberto to shed some light on this, and making him aware of the issue. @Mario, I reckon you didn't install systemd-boot and/or sdbootutil on the failing system? Do you have shim installed? I reckon /boot/efi did not exist on your system? I think Felix and Lukas nailed the problem in comment 28 and 30. kernel-default requires suse-kernel-rpm-scriptlets. This is provided by sdbootutil-rpm-scriptlets and suse-module-tools-scriptlets. sdbootutil-rpm-scriptlets has the "Supplements" shown in comment 30. But suse-module-tools-scriptlets has nothing of the kind. I wonder if adding something like Supplements: (shim unless sdbootutil) would have fixed the issue. Probably not unless shim was in the transaction set. Maybe this? Supplements: (kernel unless sdbootutil) Anyway, integrating the two scriptlets packages into one, while keeping this issue in mind, is probably the best way to move forward here. -- You are receiving this mail because: You are on the CC list for the bug.