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.
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.