My understanding of the d-i hack is that it modifies a conf file only for the ISO image, not on the actual installed system. So it shouldn't cause upgrade problems for the user.
It is true that if there were substantial changes in the mke2fs.conf file which required a config file update, this might cause problems for the d-i developers, but those would be caught in testing, and in any case (1) I'd warn them before doing anything like that, and (2) it's highly unlikely I would make any kind of backwards incompatible change since it would cause problems for the people who had their own customized mke2fs.conf already on their systems. (In general, I only add new tuning knobs to mke2fs.conf, and the defaults if something isn't specified is the previously hard-coded default; hence, there the need that a previously version of mke2fs.conf wouldn't be suitable is extremely rare.) -- Please sync e2fsprogs e2fsprogs 1.40.7-1 with Debian https://bugs.launchpad.net/bugs/197167 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
