[Bug 1226122] TW installation with bootloader not managed leaves /boot/ empty when suse-module-tools-scriptlets not installed instead of sdbootutil-rpm-scriptlets
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
https://bugzilla.suse.com/show_bug.cgi?id=1226122 https://bugzilla.suse.com/show_bug.cgi?id=1226122#c39 --- Comment #39 from Alberto Planas Dominguez <aplanas@suse.com> --- (In reply to Felix Miata from comment #38)
if no bootloader is installed, seems that sdbootutil-rpm-scriptlets is preferred by the solver.
Again, installing neither grub components nor BLS-spec components does not equate to absence of files in some co-location necessary /to/ boot. [...]
No idea what you mean. I was not talking about the installer nor the bootloader. If the user installs a kernel, suse-module-tools-scriplets will be required too. It is required by the %pre, %post et al. from the kernel spec file. It does not matter what bootloader was chosen, nor if there is a bootloader or not. The issue is that now there is a new provider for suse-module-tools-scriptlets (sdbootutil-rpm-scriptlets). So when the user installs a kernel, libsolv has two options to choose. Seems that if there is no bootloader selected, it favors sdbootutil-rpm-scriptlets to be installed, as the "Conflict: grub2" is not forbidding the installation. Note also that in this situation the installer is also irrelevant. But really, I did not understood your point. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@suse.com