update-initramfs isn’t “totally destroyed”.
ls -la /usr/sbin/update-initramfs*
lrwxrwxrwx 1 root root 26 Dec 7 2017 /usr/sbin/update-initramfs -> /bin/live-update-initramfs
-rwxr-xr-x 1 root root 7332 Jul 27 2019 /usr/sbin/update-initramfs.orig.initramfs-tools
/usr/sbin/update-initramfs was modified by pacakge live-tools to be a symlink to /bin/live-update-initramfs
The orignal update-initramfs is still available as /usr/sbin/update-initramfs.orig.initramfs-tools
Could you please have a look at both scripts? Maybe we’ll find the best way to deal with this. Maybe some way to “trick” /bin/live-update-initramfs into calling /usr/sbin/update-initramfs.orig.initramfs-tools (it does that under some conditions).
We can to undo and restore the original update-initramfs or use the original update-initramfs. Full details here: Whonix host operating system
Either before running the calamares installer:
sudo unlink /usr/sbin/update-initramfs
sudo cp /usr/sbin/update-initramfs.orig.initramfs-tools /usr/sbin/update-initramfs
That might work well enough as a workaround. Something similar could be applied during the build process.
Or modify main.py.dist to run
/usr/sbin/update-initramfs.orig.initramfs-tools (with paramater
-u? similar to default).
Maybe VirtualBox can be a good tool to conveniently test EFI booting during development? Never tried that yet. Not even with Debian.
Also as weird as that might seem, I guess I am going to add some opt-in debug option to install VirtualBox guest additions on on Whonix-Host KVM iso because that would help during development.