[Bug 2036406] Re: [SRU] backport mkeficapsule to jammy

[Dave Jones]

Trying to channel the SRU team, a couple of things I'd point out that
may need some clarification in the bug description:

* Does this also need back-porting to lunar? We shouldn't have a
situation where something is fixed in jammy but regresses for people
upgrading to lunar (ignore this if these changes are already present in
the lunar version)

* The Impact specifies what the bug is doing but not really what the
"impact" actually is. What will it mean for users if this bug is *not*
fixed? It may also be useful to describe precisely what firmware we're
talking about (typically most firmware comes from the linux-firmware
package but I'm guessing we're talking about early-boot related firmware
here).

* In the Test Case is there enough information for people other than the
reporter to test the fix?

* In the regression potential: as I understand it from the patches,
there's *some* mkeficapsule code already in the jammy version but it's
not built as part of u-boot-tools. Is that mkeficapsule code solely used
by the mkeficapsule binary, or does patching it affect anything else in
u-boot (i.e. does anything else pull in any parts of mkeficapsule)? If
not, it's probably worth mentioning that mkeficapsule is "standalone"
and these patches affect nothing other than a binary that isn't
currently built in the jammy version.

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

Title:
  [SRU] backport mkeficapsule to jammy

Status in OEM Priority Project:
  Confirmed
Status in u-boot package in Ubuntu:
  New

Bug description:
  [Impact]

  * mkeficapsule command is used to generate capsule file for updating
  firmware in u-boot

  [Test case]

  Test case 1:
  1. use mkeficapsule command to generate test_new.cap and test_old.cap, both contain U-Boot built at different time
  2. try to update the capsule file(both test_new.cap and test_old.cap)
  3. check if the U-Boot build stamp is different from previous

  Test case 2:
  1. Follow the command here(https://u-boot.readthedocs.io/en/latest/develop/testing.html#pytest-suite) to test with U-Boot sandbox, and the test_efi_capsule related files were skipped by default before or ater the code changes, the test result can be found in comment

  [Where problems could occur]

  * There is no mkeficapsule command in Jammy yet, so the regression
  risk should be low

  [Other Info]
  N/A

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