This bug was fixed in the package grub2-signed - 1.167~16.04.6 --------------- grub2-signed (1.167~16.04.6) xenial; urgency=medium
* Rebuild against grub2 2.04-1ubuntu44.1.2. LP: #1926748. grub2-signed (1.167~16.04.5) xenial; urgency=medium * Rebuild against grub2 2.04-1ubuntu44.1.1. * debian/*.postinst: Unconditionally call grub-install with --force-extra-removable, so that the \EFI\BOOT removable path as used in cloud images receives the updates. LP: #1930742. -- Steve Langasek <steve.langa...@ubuntu.com> Mon, 07 Jun 2021 13:26:45 -0700 ** Changed in: grub2-unsigned (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1926748 Title: regression in xenial updates - grub2 cannot handle new arm64 relocations Status in grub2 package in Ubuntu: Fix Released Status in grub2-signed package in Ubuntu: Invalid Status in grub2-unsigned package in Ubuntu: Invalid Status in grub2 source package in Trusty: New Status in grub2-signed source package in Trusty: New Status in grub2-unsigned source package in Trusty: New Status in grub2 source package in Xenial: Fix Released Status in grub2-signed source package in Xenial: Fix Released Status in grub2-unsigned source package in Xenial: Fix Released Status in grub2-signed source package in Bionic: Fix Released Status in grub2-unsigned source package in Bionic: Fix Released Bug description: [Impact] * regression in xenial updates - grub2 cannot handle new relocations * grub-efi-arm64-bin gained new recommends on -signed package which is attempted to be installed * it pulls in one grub which was built with a newer toolchain and has more relocations * non-secureboot grub-install in xenial fails to install it when creating core.efi, because it does not know how to handle new relocations. * We need to cherrypick patches from 2.02 (which are in bionic+) to xenial & trusty. [Test Plan] * install new grub2-common grub-common * install grub-efi-arm64-signed from xenial-updates * package installation should be successful * this is executed as part of autopkgtest upgrades when testing any package on xenial in our autopkgtest cloud [Where problems could occur] * we are rebuilding grub2 which will have to go into security pocket eventually. Thus it's best to rebuild grub2 in security pocket. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1926748/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp