Package: grub2
Version: grub2
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
apt-get dist-upgrade ignored the fact that grub2 is pinned to never and
installed grub2 anyway. update-grub promptly installed a bad configuration
file. The pin file is still present.
It is not possible to use UUID search on this system as this will not
result in a sane configuration. There are multiple paths to /, only 1
of which may be used, and the first choice on the list is not it.
* What exactly did you do (or not do) that was effective (or
ineffective)?
apt-get remove grub2
lilo -t && lilo
I know from experience that editing /boot/grub/grub.cfg is futile.
* What was the outcome of this action?
* What outcome did you expect instead?
*** End of the template - remove these template lines ***
-- System Information:
Debian Release: 9.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64
(x86_64)
Foreign Architectures: i386
Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages grub2 depends on:
pn grub-common <none>
pn grub-pc <none>
grub2 recommends no packages.
grub2 suggests no packages.
