https://bugzilla.suse.com/show_bug.cgi?id=1226122 https://bugzilla.suse.com/show_bug.cgi?id=1226122#c28 Felix Miata <mrmazda@earthlink.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|TW installation leaves |TW installation with |/boot empty |bootloader not managed | |leaves /boot/ empty when | |suse-module-tools-scriptlet | |s not installed instead of | |sdbootutil-rpm-scriptlets --- Comment #28 from Felix Miata <mrmazda@earthlink.net> --- The following two packages conflict: sdbootutil-rpm-scriptlets suse-module-tools-scriptlets sdbootutil-rpm-scriptlets also conficts with grub2-x86_64-efi and grub2-i386-pc. In a bootloader not managed installation, without something selected from within the installer to specify which, first in alphabet is the apparent winner. Right now that something appears to be only using detailed package selection, and any of suse-module-tools, grub2-x86_64-efi or grub2-i386-pc selected. It seems to me the Boot detail page ought to have a type subselection for not managed that provides a way to select which kernel installation scripts need to be provided. That might be deleting not managed and adding two to replace it, a Boot Loader Specification style utility set (sdbootutil) and a traditional (grub) boot style utility set, which, like existing selections, are mutually exclusive. -- You are receiving this mail because: You are on the CC list for the bug.