Bug#1031325: e2fsprogs 1.47.0 introduces a breaking change into Bookworm, breaking grub and making installations of Ubuntu and Debian releases via debootstrap impossible
On Fri, Feb 17, 2023 at 02:08:28PM -0500, Theodore Ts'o wrote:
>...
> So enabling what may be
> convenient, but ultimately an anti-pattern is something that hopefully
> in the long-term Debian should be striving towards. Yes, it's
> annoying and and extra work. So is using build chroots if we are
> building packages for a older Distro versions. But it's the right
> thing to do.
Don't assume "host = target" would always be possible.
Your proposed solution only works for the trivial
"building Debian on Debian" case.
The same general problem applies in various "building non-Debian
embedded Linux filesystem on Debian" situations where the target
chroot does not contain mkfs.ext4.
Or if it is present, it would be a chroot for the target architecture
where you might have to run mkfs.ext4 under qemu.
All image building tools that support bookworm (including all image
building tools we ship in bookworm) have to ensure that what they
produce works on the intended target. There is no general solution
*how* to do that that could be applied in all cases.
> Secondly, (b) there may be a misapprehension that it is possible to
> get an identical file system just by controlling the contents of
> mke2fs and/or specifying the file system features on the command line.
>...
It is clear that different versions of tools like mkfs.ext4 or gzip
might produce different output.
If identical results matter, you can just define $distribution as
build environment and then expect that for example the host tools
from Debian bookworm will always create the same output when building
a Yocto distribution.
> Best regards,
>
> - Ted
cu
Adrian
Reply to: