[Bug 2003365] Re: 2022v1 resigning

Steve Langasek 2003365 at bugs.launchpad.net
Mon Jan 30 15:44:09 UTC 2023


Hello Julian, or anyone else affected,

Accepted fwupd-efi into jammy-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/fwupd-
efi/1:1.2-3ubuntu0.2 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-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. 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: fwupd-efi (Ubuntu Jammy)
       Status: New => Fix Committed

** Tags removed: verification-done-jammy
** Tags added: verification-needed-jammy

** Changed in: fwupd-signed (Ubuntu Jammy)
       Status: In Progress => Fix Committed

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

Title:
  2022v1 resigning

Status in fwupd-efi package in Ubuntu:
  New
Status in fwupd-signed package in Ubuntu:
  Fix Committed
Status in fwupd-efi source package in Bionic:
  New
Status in fwupd-signed source package in Bionic:
  In Progress
Status in fwupd-efi source package in Focal:
  New
Status in fwupd-signed source package in Focal:
  In Progress
Status in fwupd-efi source package in Jammy:
  Fix Committed
Status in fwupd-signed source package in Jammy:
  Fix Committed
Status in fwupd-efi source package in Kinetic:
  Fix Committed
Status in fwupd-signed source package in Kinetic:
  Fix Committed
Status in fwupd-efi source package in Lunar:
  New
Status in fwupd-signed source package in Lunar:
  Fix Committed

Bug description:
  [Impact]
  Resign with new 2022v1 key, as the old key is revoked in shim 15.7-0ubuntu1.

  [Test plan]
  Check that fwupd.efi can be started from old and new shim.

  [Where problems could occur]
  We're building one signed binary for stable releases in kinetic now and copying it back. We last built it in jammy, there may be toolchain related regressions.

  [Other info]
  We have backported 1.51 wholesale. This matters mostly for focal as it had different version numbers so far, but the content was otherwise identical to 1.42.

  This makes it clear that 1.51 is version signed with the new key and
  where it is available, and saves a lot of time vs changing changelogs
  to incorporate separate focal history in those ~20 uploads we do for
  the rotation.

  fwupd-efi was built in kinetic in the ppa:ubuntu-uefi-team/ppa and
  then signed with the 2022v1 signing key, copied to ppa:ubuntu-uefi-
  team/proposed and then copied (--unembargo) into ppa:ubuntu-uefi-
  team/proposed-step before being copied to the main queues. The final
  proposed-public should allow sensible SRU review.

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




More information about the foundations-bugs mailing list