Bug#966575: grub-pc: Bailing out if the boot device from the debconf database does not longer exist might produce a more complicated issue

[Daniel Leidert]

Hi Colin,

I recently stumbled into this issue myself. Reading your explanation was very
helpful. However the way you fixed it produces another issue as described here:

https://forum.openmediavault.org/index.php?thread/37903-grub-related-error-on-5-5-23-update/

The command suggested by the error message (dpkg-reconfigure) actually doesn't
work if grub-pc is not fully installed. I don't have a technical solution
myself, but bailing out creates an even worse situation here. Maybe instead of
bailing out print a warning instead?

I was also thinking: If this cannot be handled in a technical way this should
definitely be mentioned in the release notes.

Regards, Daniel
-- 
Regards,
Daniel Leidert <dleidert at debian.org> | https://www.wgdd.de/
GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D
GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78

If you like my work consider sponsoring me via
https://www.patreon.com/join/dleidert
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
URL: <http://alioth-lists.debian.net/pipermail/pkg-grub-devel/attachments/20210211/23fef64e/attachment.sig>