[Bug 1926748] Re: regression in xenial updates - grub2 cannot handle new arm64 relocations

[Julian Andres Klode]

I reran the update-notifier test that failed with grub error in xenial
with the new grub added as trigger, and it installed now, so it's good
to go :D

Unpacking grub-efi-arm64 (2.04-1ubuntu44) over (2.02~beta2-36ubuntu3.29) ...
Preparing to unpack .../grub-efi-arm64-bin_2.04-1ubuntu44_arm64.deb ...
Unpacking grub-efi-arm64-bin (2.04-1ubuntu44) over (2.02~beta2-36ubuntu3.29) ...
Preparing to unpack .../grub2-common_2.02~beta2-36ubuntu3.32_arm64.deb ...
Unpacking grub2-common (2.02~beta2-36ubuntu3.32) over (2.02~beta2-36ubuntu3.29) ...
Preparing to unpack .../grub-common_2.02~beta2-36ubuntu3.32_arm64.deb ...
Unpacking grub-common (2.02~beta2-36ubuntu3.32) over (2.02~beta2-36ubuntu3.29) ...
Selecting previously unselected package grub-efi-arm64-signed.
Preparing to unpack .../grub-efi-arm64-signed_1.167~16.04.1+2.04-1ubuntu44_arm64.deb ...
Unpacking grub-efi-arm64-signed (1.167~16.04.1+2.04-1ubuntu44) ...
Processing triggers for install-info (6.1.0.dfsg.1-5) ...
Processing triggers for man-db (2.7.5-1) ...
Processing triggers for systemd (229-4ubuntu21.31) ...
Setting up python-apt-common (1.1.0~beta1ubuntu0.16.04.12) ...
Setting up python3-apt (1.1.0~beta1ubuntu0.16.04.12) ...
Setting up grub-common (2.02~beta2-36ubuntu3.32) ...
update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
Setting up grub-efi-arm64-bin (2.04-1ubuntu44) ...
Setting up grub2-common (2.02~beta2-36ubuntu3.32) ...
Setting up grub-efi-arm64 (2.04-1ubuntu44) ...
Installing for arm64-efi platform.
Installation finished. No error reported.
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-210-generic
Found initrd image: /boot/initrd.img-4.4.0-210-generic
Adding boot menu entry for EFI firmware configuration
done
Setting up grub-efi-arm64-signed (1.167~16.04.1+2.04-1ubuntu44) ...
Installing for arm64-efi platform.
Installation finished. No error reported.
Reading package lists...
Building dependency tree...
Reading state information...


** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done verification-done-xenial

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to grub2 in Ubuntu.
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 source package in Trusty:
  New
Status in grub2 source package in Xenial:
  Fix Committed

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