[SRU] [HWE] Backport efibootmgr 0.12-4 to 15.04
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
efibootmgr (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
[Impact]
Shipping fwupdate in 15.04 (hardware enablement tool; a firmware updater tool) requires the use of efivar > 0.16; which in turn requires a slightly newer version of efibootmgr (at least 0.12-2).
[Test Case]
- Install libefivar0.
Installing libefivar0 will attempt to remove efibootmgr, which is quite unhelpful when one has to deal with EFI boot entries. Furthermore, efibootmgr is a Dependency of grub EFI images, of which the removal would likely be catastrophic to booting the system.
[Regression Potential]
Issues in efibootmgr would show up as the inability to configure new (or modify old) EFI boot entries; for example inability to install a boot image on some specific disks.
efibootmgr is critical to the proper function of grub updates for EFI systems.
This is a new upstream version of efibootmgr, which has implications well beyond the new version of fwupdate that this is intended to facilitate.
Why is the breaks against 0.12-2? (vs. 0.12-1) If there is a specific distro patch in 0.12-2, then I believe we should cherry-pick that patch into vivid efibootmgr if possible, and adjust the breaks on the version of efibootmgr in vivid. If that isn't possible (because the patch doesn't cherry-pick cleanly) we will need more detailed analysis of the upstream changes between 0.11.0 and 0.12 to confirm that these are sufficently low-risk.