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 Thu, Feb 16, 2023 at 05:24:04PM -0500, Theodore Ts'o wrote:
>...
> and that moving forward, we make it the image building tools
> problem if they want to support this highly dubious practice of using
> Debian N+X's mkfs to build images for Debian N.
>...
That's what they already have to do for many years.
But it is also our problem when we ship these image building tools,
to ensure that there are bugs against all of them that get fixed
before the release where the change is present.
> Best release engineering practice is that you use a known, controlled
> build environment, and not whatever random package versions might be
> on your desktop. While that might be "inconvenient" when building
> packages, we've learned to live with it. I use sbuild; others might
> use pbuild, or their own custom schroot setup. But I dare say all
> responsible people doing release engineering use a known build
> environment. Why should this be any different if you are building
> images --- especially images that you expect *your* users or customers
> to be depending on?
>...
controlled != identical to the target
There are different approaches to this problem with different advantages
and disadvantages.
It is not unreasonable for an image building tool we ship in bookworm to
use the host tools of a bookworm x86 server to create a Debian image for
a buster ARM target.
> - Ted
cu
Adrian
Reply to: