On Thu, Feb 16, 2023 at 05:48:22PM +0100, Daniel Leidert wrote: > Am Donnerstag, dem 16.02.2023 um 18:37 +0200 schrieb Adrian Bunk: > > On Wed, Feb 15, 2023 at 12:05:41AM +0100, Daniel Leidert wrote: > > > ... > > > Reasons: > > > ... > > > - - the change makes it impossible to create filesystems with this > > > version of > > > e2fsprogs and then run a grub-install from a target system that does > > > not cope > > > with that feature; basically breaking the debootstrap method of > > > installing > > > Debian or Ubuntu onto a server (violating #4 of the Debian social > > > contract) > > > ... > > > Instead, turning on this feature should be postponed for the next release > > > cycle > > > where a proper transition can be done. > > > ... > > > > Daniel, you are contradicting yourself when claiming that a change that > > would allegedly violate the Debian social contract could be done in the > > next release cycle. > > Actually, I'm not. >...
If not being able to install bullseye from bookworm is a violation of the Debian social contract, then the same rationale applies to not being able to install bullseye from trixie being a violation of the Debian social contract. In [1] you are arguing with problems installing Ubuntu 20.04 this way from bookworm with the e2fsprogs change, the same will apply to installing Ubuntu 22.04 from trixie. QED > I have also written in [1] how I think the transition > should be handled (IMO) >... I am currently spending time trying to summarize the situation and open questions, and I am a bit underwhelmed by the inaccuracies and lack of technical detail in your emails. The instructions you cite in [1] are for installing bullseye from non-Debian systems. What bookworm ships does not matter much there, these instructions will be wrong as soon as some *other* distribution like Fedora changes the default. I am wondering how exactly your often repeated "there is no grub upstream release with support for it" would be relevant in practice. Whether it's 2.06-8 or 2.07-1 in bookworm shouldn't make a difference. Sebastian has now created #1031364 for your original vmdb2 problem, everyone discussing in #1030939 seems to have missed that tools in bookworm creating images for < bookworm must handle such changes. That's not different from debootstrap having code to handle apt-transport-https being required in some older releases. > [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030939#108 > > Regards, Daniel cu Adrian