https://bugzilla.suse.com/show_bug.cgi?id=1228759 https://bugzilla.suse.com/show_bug.cgi?id=1228759#c12 Michal Suchanek <msuchanek@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mls@suse.com Flags| |needinfo?(mls@suse.com) --- Comment #12 from Michal Suchanek <msuchanek@suse.com> --- An optional support for sdboot was added to suse-module-tools in Factory recently. suse-module-tools and suse-module-tools-scriptlets are used from kernel-default and kernel-longterm rpm scripts, and the kernel depends on them. The scripts in turn detect if sdbootutil is installed, and if so enable the sdboot features. However, when systemd is being upgraded in the same transaction as the kernel the sdboot tools might be in inconsistent state when the kernel rpm scripts run - the systemd library is upgraded but the systemd-sdboot is not. Presumably this is because suse-module-tools and suse-module-tools-scriptlets declare no rpm dependency on sdbootutil and only detect sdboot support at runtime. What is the correct dependency to declare on sdbootutil to make sure it is in consistent state when installed? -- You are receiving this mail because: You are on the CC list for the bug.