> It turns out that while there is no signed *fwupd* on xenial, there is a
> signed *fwupdate*, so releasing this update would break firmware
> updating after all :/

Not a blocker.  fwupdate is obsolete, cannot be trivially migrated to
fwupd (the SRU of fwupd-signed in bionic was quite painful), and already
lacks support for a lot of relevant firmware updates.  On behalf of the
SRU team, I had already taken the decision to allow fwupdate-signed to
regress in xenial in favor of continued SecureBoot support.

** Tags removed: block-proposed-xenial

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

Title:
  SBAT shim 15.4 release

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1921134/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to