[Bug 2011804] Re: [SRU] [HWE] gnu-efi 3.0.15

[Steve Langasek]

Hello Julian, or anyone else affected,

Accepted gnu-efi into kinetic-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/gnu-
efi/3.0.15-1~22.10.1 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-
kinetic to verification-done-kinetic. If it does not fix the bug for
you, please add a comment stating that, and change the tag to
verification-failed-kinetic. 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/PerformingSRUVerification .  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.

** Changed in: gnu-efi (Ubuntu Kinetic)
       Status: Triaged => Fix Committed

** Tags added: verification-needed verification-needed-kinetic

** Description changed:

  [Impact]
  gnu-efi 3.0.15 is required for fwupd-efi 1.4 to work correctly on firmware requiring NX memory in boot stack.
  
  Updating gnu-efi also ensures that all our fwupd-efi 1.4 binaries ship
  the same code which makes it easier to reason about security
  vulnerabilities.
  
  [Workflow]
  gnu-efi is built in ppa:ubuntu-uefi-team/ubuntu/ppa against the security  pocket only following the in-progress signed boot asset workflow.
  
  [Target releases]
  We are only building boot assets on the latest stable release, so will SRU that only to kinetic. Rebuilding the boot assets in older stable releases should still work though, they do not technically require gnu-efi 3.0.15 for building (fwupd-efi actually doesn't build due to debhelper 13 dependency).
  
  The tasks have been set to Won't Fix on older releases to make this
  clear, but this is not a hard decision, if we fix fwupd-efi to build on
  those releases and it turns out we need gnu-efi 3.0.15 anyhow, we can
  still upload it, but of course this increases regression potential for
  those releases.
  
  [Test plan]
- We can't test the NX support yet as we do not have a shim with NX support. Test that fwupd-efi 1.4 builds. Also test and fix any reverse build depends regressions in main.
+ We can't test the NX support yet as we do not have a shim with NX support. Test that fwupd-efi 1.4 builds. Also test and fix any reverse build depends regressions in the archive.
  
  We will test NX support when we work on the NX supported shim.
  
  [Where problems could occur]
  To my knowledge, fwupd-efi is the only supported component in the archive that uses gnu-efi. Some more binaries are built with gnu-efi and might regress, e.g. systemd.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to gnu-efi in Ubuntu.
https://bugs.launchpad.net/bugs/2011804

Title:
  [SRU] [HWE] gnu-efi 3.0.15

Status in gnu-efi package in Ubuntu:
  Fix Released
Status in gnu-efi source package in Bionic:
  Won't Fix
Status in gnu-efi source package in Focal:
  Won't Fix
Status in gnu-efi source package in Jammy:
  Won't Fix
Status in gnu-efi source package in Kinetic:
  Fix Committed

Bug description:
  [Impact]
  gnu-efi 3.0.15 is required for fwupd-efi 1.4 to work correctly on firmware requiring NX memory in boot stack.

  Updating gnu-efi also ensures that all our fwupd-efi 1.4 binaries ship
  the same code which makes it easier to reason about security
  vulnerabilities.

  [Workflow]
  gnu-efi is built in ppa:ubuntu-uefi-team/ubuntu/ppa against the security  pocket only following the in-progress signed boot asset workflow.

  [Target releases]
  We are only building boot assets on the latest stable release, so will SRU that only to kinetic. Rebuilding the boot assets in older stable releases should still work though, they do not technically require gnu-efi 3.0.15 for building (fwupd-efi actually doesn't build due to debhelper 13 dependency).

  The tasks have been set to Won't Fix on older releases to make this
  clear, but this is not a hard decision, if we fix fwupd-efi to build
  on those releases and it turns out we need gnu-efi 3.0.15 anyhow, we
  can still upload it, but of course this increases regression potential
  for those releases.

  [Test plan]
  We can't test the NX support yet as we do not have a shim with NX support. Test that fwupd-efi 1.4 builds. Also test and fix any reverse build depends regressions in the archive.

  We will test NX support when we work on the NX supported shim.

  [Where problems could occur]
  To my knowledge, fwupd-efi is the only supported component in the archive that uses gnu-efi. Some more binaries are built with gnu-efi and might regress, e.g. systemd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnu-efi/+bug/2011804/+subscriptions