On Sat, 2020-03-28 at 22:50 +0100, Cyril Brulebois wrote: > Hallo Bernhard, > > Bernhard <bewoe...@gmail.com> (2020-03-28): > > My system don't start in case of Secure Boot is enabled. > > > > In Debian Wiki: https://wiki.debian.org/SecureBoot > > The package grub-efi-amd64-signed is not installed. > > This is a recommended package. > > But this package is necessary for Secure Boot. > > > > If i install a standard Debian installation, my system boot with Secure > > Boot. > > With a standard Debian installation, the recommended packages will be > > installed also. > > Oh, we do install grub-efi-amd64 which Depends: grub-efi-amd64-bin which > itself Recommends: grub-efi-amd64-signed. > > So either stop disabling Recommends (you're working against the default > setting, you're supposed to be dealing with the consequences on your > own), or additionally install grub-efi-amd64-signed through appropriate > parameters in your preseed file. > > This seems to me like a not-a-bug situation.
It is definitely a bug that we automatically install shim-signed without grub-efi-amd64-signed. That combination doesn't make any sense. Ben. > Leaving this open for other members of the installer team to comment, > but as far as I can tell, this bug report could likely be closed right > away. > > > Cheers, -- Ben Hutchings This sentence contradicts itself - no actually it doesn't.
signature.asc
Description: This is a digitally signed message part
