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