Bug#1030846: e2fsprogs: generates filesystems that grub-install doesn't recognize

[Daniel Leidert]

Hi Steve,

I believe that your fix to grub2 in Sid is not enough to handle
#1030939/#1030846.

This problem breaks e.g. vmdb2. I can no longer create a Bullseye
system image with vmdb2 on Sid, because the grub-install step in the
Bullseye chroot now fails, because the created filesystem (created with
e2fsprogs on Sid) cannot be recognized by grub. I have to downgrade
e2fsprogs to the version in Testing to get the build going again. It
also means that a Bookworm system can never be used to format and
debootstrap a Bullseye or Buster system that requires a grub
installation.

I guess that the fix applied to grub2 in Sid would have to be applied
to grub2 in Bullseye as well (and basically to any grub2 package in any
Debian or Ubuntu or Raspbian release supported by debootstrap).

This situation is really messy. It breaks basically all my image builds
with vmdb2.

Regards, Daniel
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 862 bytes
Desc: This is a digitally signed message part
URL: <http://alioth-lists.debian.net/pipermail/pkg-grub-devel/attachments/20230214/cfc3f34e/attachment.sig>