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 09:28:59PM -0500, Theodore Ts'o wrote:
> On Fri, Feb 17, 2023 at 10:34:29PM +0200, Adrian Bunk wrote:
> >
> > 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.
>
> In practice, if the root file system is using ext4, the target chroot
> has to have e2fsprogs installed so that fsck.ext4 exists. So I'm not
> sure it's all that unreasonable?
>...
In Yocto e2fsprogs-e2fsck and e2fsprogs-mke2fs are separate packages.
The general problem is also not limited to mkfs.
The target might have busybox tar, but you might want to use GNU tar for
generating tarballs that will be unpacked on the target.
I have once seen some old version of busybox tar choke on some specific
tarball generated by GNU tar, but that's not a reason for a general rule
that all tarballs that might be unpackaged on the target must be created
by busybox tar.
I do see your point that reducing differences between host tools and
target can be desirable, but there are limits how far this is feasible
or whether it is the best solution in a given situation.
When differences exist, it is the responsibility of the image creation
tools to deal with the differences.
> Best regards,
>
> - Ted
cu
Adrian
Reply to: