On Tue, Jun 04, 2024 at 02:33:27PM +0200, Fabio Fantoni wrote: > Package: e2fsprogs > Version: 1.47.1~rc2-1~bpo12+1 > Severity: important > > Dear Maintainer, > > After a debug of a issue with backup I spotted that the cause was > metadata_csum_seed and orphan_file enabled by default in e2fsprogs from > bookworm-backports. > These were already disabled for bookworm as I saw in 2 RC bugs: #1031622, > #1030939 > I think is good disable them also in bookworm-backports builds, can you do it > please? > For now I found a workaround with manual change to /etc/mke2fs.conf before > create new ext4 fs but I think is useful do it by default to avoid issues and > waste of time for other users.
Hi Fabio, Debian backports policy is that package is supposed to exactly the same (as much as possible, anyway) as what is in Debian testing. I'll also note that (a) bookworm-backports has a version of grub2 that supports metadata_csum, and (b) the debian-backports web page[1] states that "there is a risk of incompatibilities with other components in Debian stable, so backports should be used with care!" and (c) the page[1] further states "All backports are deactivated by default so that the normal operation of a stable installation will not be compromised with potentially disruptive changes (such as incompatible configuration schema)." [1] https://backports.debian.org/Instructions/ As such, I believe that it is both reasonable and in accordance with backports policy that e2fsprogs in bookworm-backports mirror what will be the case in Debian Trixie (current Debian testing). Best regards, - Ted
