Felix Miata changed bug 1226122
What Removed Added
Summary TW installation leaves /boot empty TW installation with bootloader not managed leaves /boot/ empty when suse-module-tools-scriptlets not installed instead of sdbootutil-rpm-scriptlets

Comment # 28 on bug 1226122 from Felix Miata
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: