regression in xenial updates - grub2 cannot handle new arm64 relocations
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
grub2 (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Trusty |
Confirmed
|
Undecided
|
Unassigned | ||
Xenial |
Fix Released
|
Undecided
|
Unassigned | ||
grub2-signed (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Trusty |
Confirmed
|
Undecided
|
Unassigned | ||
Xenial |
Fix Released
|
Undecided
|
Unassigned | ||
Bionic |
Fix Released
|
Undecided
|
Unassigned | ||
grub2-unsigned (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Trusty |
Confirmed
|
Undecided
|
Unassigned | ||
Xenial |
Fix Released
|
Undecided
|
Unassigned | ||
Bionic |
Fix Released
|
Undecided
|
Unassigned | ||
Jammy |
Fix Released
|
Undecided
|
Unassigned |
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-
* 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.
CVE References
tags: |
added: regresion-update-xenial regression-update xenial removed: regression-up |
Changed in grub2 (Ubuntu): | |
status: | New → Fix Released |
description: | updated |
Changed in grub2-unsigned (Ubuntu): | |
status: | New → Invalid |
Changed in grub2-signed (Ubuntu): | |
status: | New → Invalid |
Changed in grub2-signed (Ubuntu): | |
status: | Invalid → Fix Released |
Changed in grub2-unsigned (Ubuntu): | |
status: | Invalid → Fix Released |
tags: | removed: regresion-update-xenial |
Hello Dimitri, or anyone else affected,
Accepted grub2 into xenial-proposed. The package will build now and be available at https:/ /launchpad. net/ubuntu/ +source/ grub2/2. 02~beta2- 36ubuntu3. 32 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https:/ /wiki.ubuntu. com/Testing/ EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification- needed- xenial to verification- done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed- xenial. In either case, without details of your testing we will not be able to proceed.
Further information regarding the verification process can be found at https:/ /wiki.ubuntu. com/QATeam/ PerformingSRUVe rification . Thank you in advance for helping!
N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.