Public bug reported:
[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.
** Affects: grub2 (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: grub2 (Ubuntu Trusty)
Importance: Undecided
Status: New
** Affects: grub2 (Ubuntu Xenial)
Importance: Undecided
Status: New
** Tags: regresion-update-xenial regression-update xenial
** Tags removed: regression-up
** Tags added: regresion-update-xenial regression-update xenial
** Also affects: grub2 (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: grub2 (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: grub2 (Ubuntu)
Status: New => Fix Released
** Description changed:
[Impact]
- * regression in xenial updates - grub2 cannot handle new relocations
+ * regression in xenial updates - grub2 cannot handle new relocations
- * grub-efi-arm64-bin gained new recommends on -signed package which is
+ * 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
+ * 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
+ * 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 new grub2-common grub-common
- * install grub-efi-arm64-signed from xenial-updates
+ * install grub-efi-arm64-signed from xenial-updates
- * package installation should be successful
+ * package installation should be successful
- * this is executed as part of autopkgtest upgrades when testing any
+ * 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
+ * we are rebuilding grub2 which will have to go into security pocket
eventually. Thus it's best to rebuild grub2 in security pocket.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926748
Title:
regression in xenial updates - grub2 cannot handle new arm64
relocations
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1926748/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
