← Back to team overview

group.of.nepali.translators team mailing list archive

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

 

This bug was fixed in the package grub2 - 2.02~beta2-36ubuntu3.32

---------------
grub2 (2.02~beta2-36ubuntu3.32) xenial; urgency=medium

  * Cherrypick upstream commit to add support for
    R_AARCH64_ADR_PREL_PG_HI21, R_AARCH64_ADD_ABS_LO12_NC,
    R_AARCH64_LDST64_ABS_LO12_NC relocations in grub-install / mkimage to
    allow generating and installing grub.efi from one-grub modules. LP:
    #1926748

grub2 (2.02~beta2-36ubuntu3.31) xenial; urgency=medium

  [ Dimitri John Ledkov & Steve Langasek ]
  * Relax dependencies to allow grub-efi be installed with later versions
    of grub-efi-amd64. Stop building grub-efi-amd64|arm64{-bin,dbg}
    packages, now provided by src:grub2-unsigned. LP: #1915536

  [ Dimitri John Ledkov ]
  * Cherrypick 2.02+dfsg1-5 patch for x86-64: Treat R_X86_64_PLT32 as
    R_X86_64_PC32 to allow processing 2.04 grub modules built with newer
    binutils.

 -- Dimitri John Ledkov <xnox@xxxxxxxxxx>  Fri, 30 Apr 2021 13:33:21
+0100

** Changed in: grub2 (Ubuntu Xenial)
       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 source package in Trusty:
  New
Status in grub2 source package in Xenial:
  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


References