Comment 2 for bug 1787254

As an archive admin I've said that we should not be signing two parallel streams of EFI binaries implementing this functionality. If fwupd is considered the preferred implementation upstream and Ubuntu is going to adopt this, then we should remove fwupdate-signed entirely from the archive and stop producing artifacts from fwupdate source package for EFI signing.

If there are design reasons why Ubuntu Core should prefer fwupx64.efi over fwupdx64.efi going forward, then we should clarify what these are and evaluate whether Ubuntu classic should follow suit. Otherwise, we should drop fwupdate-signed from the archive, adjust the fwupdate source package to not generate EFI artifacts for signing, and ensure that snapd migrates to fwupd by 20.04.

John, I suggested your name to Mario as a possible first contact for this on the Snappy side, but please escalate this as appropriate.

NB I can't see anywhere in the snapd code or in the pc gadget snap where fwupx64.efi is ever installed to the ESP, so it's entirely unclear to me how this currently works on Ubuntu Core either.