On Sun, 19 Feb 2023 19:01:22 +0100 Paul Gevers <elb...@debian.org> wrote:
> On 2023-02-15 21:04:36 +0100, Sebastian Ramacher wrote:> > > > On 2023-02-14 01:01:38 +0100, Daniel Leidert wrote: > > > > > > This problem breaks e.g. vmdb2. I can no longer create a Bullseye> > > system image with vmdb2 on Sid, because the grub-install step in the > > > Bullseye chroot now fails, because the created filesystem (created with > > > e2fsprogs on Sid) cannot be recognized by grub. I have to downgrade > > > e2fsprogs to the version in Testing to get the build going again. It > > > also means that a Bookworm system can never be used to format and > > > debootstrap a Bullseye or Buster system that requires a grub > > > installation.> > > > > > I guess that the fix applied to grub2 in Sid would have to be applied> > > to grub2 in Bullseye as well (and basically to any grub2 package in any > > > Debian or Ubuntu or Raspbian release supported by debootstrap).> > > > > > This situation is really messy. It breaks basically all my image builds> > > with vmdb2.> > > > Regardless of the outcome of #1031325, this issue will need to be fixed> > in vmdb2 eventually. vmdb2, similar to other bootstraping tools, has to > > account for the feature and disable it if necessary for older > > distributions.> > > > Cloning and reassign to vmdb2. > > Based on more feedback from #10313225, I am also cloning and reassigning> this issue to fai and grml-debootstrap. Dear maintainers, please check > whether this issue is relevant for your packages.The same appears to apply for debos and freedom-maker. Dear maintainers, please check whether this issue is relevant for your packages.
Control: severity -1 normal
The images built by freedom-maker have btrfs root partition by default, which
are not affected by e2fsprogs. Although freedom-maker includes code to support
ext4 root partition, to actually build an image using ext4 requires patching
the source code of freedom-maker. If one modifies freedom-maker in this way,
then there will be an error if building a bullseye image on a bookworm host:
2023-02-23 13:08:25,297 - ERROR - Target failed - virtualbox-amd64-ext4
Traceback (most recent call last):
File "<frozen runpy>", line 198, in _run_module_as_main
File "<frozen runpy>", line 88, in _run_code
File "/home/james/salsa/freedombox-team/freedom-maker/freedommaker/__main__.py",
line 13, in <module>
Application().run()
File
"/home/james/salsa/freedombox-team/freedom-maker/freedommaker/application.py",
line 57, in run
builder.build()
File
"/home/james/salsa/freedombox-team/freedom-maker/freedommaker/builders/vm.py",
line 21, in build
self.make_image()
File
"/home/james/salsa/freedombox-team/freedom-maker/freedommaker/builder.py", line
106, in make_image
self._get_builder_backend().make_image()
File
"/home/james/salsa/freedombox-team/freedom-maker/freedommaker/internal.py",
line 43, in make_image
self._install_boot_loader()
File
"/home/james/salsa/freedombox-team/freedom-maker/freedommaker/internal.py",
line 352, in _install_boot_loader
library.install_grub(self.state)
File
"/home/james/salsa/freedombox-team/freedom-maker/freedommaker/library.py", line
476, in install_grub
run_in_chroot(state, ['grub-install', device] + args)
File
"/home/james/salsa/freedombox-team/freedom-maker/freedommaker/library.py", line
49, in run_in_chroot
return run(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^
File
"/home/james/salsa/freedombox-team/freedom-maker/freedommaker/library.py", line
43, in run
return cliapp.runcmd(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/cliapp/runcmd.py", line 64, in runcmd
raise cliapp.AppException(msg)
cliapp.app.AppException: Command failed: chroot /tmp/tmpxa690dib grub-install
/dev/loop0
b''
b'Installing for i386-pc platform.\ngrub-install: error: unknown filesystem.\n'
Building a bookworm image that uses ext4 does not have this error.
In addition, it's not clear to me that there is a requirement for freedom-maker
in bookworm to build bullseye images.
OpenPGP_signature
Description: OpenPGP digital signature
