* Sebastian Ramacher [Thu Feb 16, 2023 at 09:09:08AM +0100]: > On 2023-02-15 13:17:38 -0700, Sam Hartman wrote:
> > But for example you're not leaving a lot of time for asking programs > > like vmdb2 or fai-diskimage to adjust how they call fsck. > > If you made this change a few months ago, it would be reasonable to file > > bugs against those packages and ask them to adjust how they call > > mkfs.ext4. > To better understand the impact of this change, I was wondering which > tools / image builders in the archive would be affected by this change. > I've cloned the bug to vmdb2, but what about others? I didn't verify it yet, but AFAICT grml-debootstrap is affected as well, since it supports installing older Debian releases from within more recent Debian/Grml environments and uses mkfs.ext4 as default. BTW, we had a similar situation already in the past when mkfs.ext4 of e2fsprogs >=1.43~WIP.2015.05.18-1 enabled the "metadata_csum" feature, while this was unsupported on jessie and older releases. (grml-debootstrap provides a workaround for this.) regards -mika-
signature.asc
Description: PGP signature
