Comment 7 for bug 1917509

The grub2 in xenial-proposed seems to break at least on arm64 on the autopkgtest environment:

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/arm64/l/linux-hwe/20210309_043356_9f6d6@/log.gz

--
[...]
Setting up grub-common (2.02~beta2-36ubuntu3.31) ...
update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
Setting up grub-efi-arm64-bin (2.04-1ubuntu42) ...
Setting up grub2-common (2.02~beta2-36ubuntu3.31) ...
Setting up grub-efi-arm64 (2.04-1ubuntu42) ...
Installing for arm64-efi platform.
grub-install: error: relocation 0x113 is not implemented yet.
Failed: grub-install --target=arm64-efi
WARNING: Bootloader is not properly installed, system may not be bootable
Generating grub configuration file ...
Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is set is no longer supported.
Found linux image: /boot/vmlinuz-4.4.0-204-generic
Found initrd image: /boot/initrd.img-4.4.0-204-generic
Found linux image: /boot/vmlinuz-4.4.0-203-generic
Found initrd image: /boot/initrd.img-4.4.0-203-generic
Adding boot menu entry for EFI firmware configuration
done
Setting up grub-efi-arm64-signed (1.164+2.04-1ubuntu42) ...
Installing for arm64-efi platform.
grub-install: error: relocation 0x113 is not implemented yet.
dpkg: error processing package grub-efi-arm64-signed (--configure):
 subprocess installed post-installation script returned error exit status 1