[Bug 1820768] Re: [SRU] support new cab and new docking firmware upgrade in fwupd 1.2.5

[Mario Limonciello]

Per comment #8 and #9, #12

I would like to clarify that the way it works with newer fwupd is that
the binary is installed into the EFI system partition dynamically as
needed rather than at install time.  This means that only people that
are performing firmware upgrades would have the file installed.

A sample link to the code in question that accomplishes this:
https://github.com/hughsie/fwupd/blob/master/plugins/uefi/fu-uefi-bootmgr.c#L341

Where are we at in an terms of review on this SRU?

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

Title:
  [SRU] support new cab and new docking firmware upgrade in fwupd 1.2.5

Status in OEM Priority Project:
  In Progress
Status in fwupd package in Ubuntu:
  Fix Released
Status in fwupd-signed package in Ubuntu:
  Fix Released
Status in libxmlb package in Ubuntu:
  Fix Released
Status in fwupd source package in Bionic:
  Fix Committed
Status in fwupd-signed source package in Bionic:
  Fix Committed
Status in libxmlb source package in Bionic:
  Fix Committed

Bug description:
  * Impact

  Bios vendor is pushing to put the new design into cab file, and also
  new docking DW19 needs the new fwupd to support it.

  That needs new fwupd to support.

  * Test case

  I
  1. install the new fwupd, and plugin the new docking - DW19.
  2. fwupdmgr get-devices and check if all internal device can properly show
  II.
  1. If you can get new cab file, try to use fwupdmgr install XX.cab to see if can work properly.
  III.
  1. If you can get a machine that have some firmware update pending, try to go gnome-software, and click refresh with the new fwupd, you should be able to see the pending firmware showed there. Which proves that it can properly be integrated with gnome. (ycheng-twn have a laptop with that condition, and he can verify that one)
  IV. As we need to remove fwupdate-signed and install fwupd-sign, we need to test if fwupdate(bionic) work well with fwupd-signed(the new verion in this SRU)

  * Regression potential

  
  Since the upstream maintainer is back up this upgrade, and he also works in a major computer vendor and works closely with the BIOS team, it should be fairly low risk.

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