Package: grub-coreboot Version: 2.02-2 Severity: normal Seems that while grub-pc creates /boot/grub in passing (before putting some files in there), grub-coreboot and perhaps other grubs does not. So, installing grub and then running grub-mkconfig may fail, due to the directory not existing.
That seems like an inconsistency that's worth making consistent. I noticed because propellor assumed it could do that for all grubs. Probably d-i does something else that creates /boot/grub before grub-mkconfig ever gets run, which is why this inconsistency has not been noticed. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.14.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages grub-coreboot depends on: ii debconf [debconf-2.0] 1.5.65 ii dpkg 1.19.0.4 ii grub-common 2.02-2 pn grub-coreboot-bin <none> ii grub2-common 2.02-2 ii ucf 3.0036 grub-coreboot recommends no packages. grub-coreboot suggests no packages. -- see shy jo
signature.asc
Description: PGP signature
