[Bug 2116176] [NEW] Backport fwupd 1.9 to jammy

Tue Jul 8 13:13:04 UTC 2025

Public bug reported:

[Impact]
Machines on jammy no longer receive firmware security updates, as the LVFS server seemingly has blocked the old version. While they can presumably install older versions of the firmware, they are unable to get new firmware versions.

This requires a backport of meson in turn. This bug includes the
backport of meson-1.5 from the 24.04.2 HWE stack.

A backport of libxmlb 0.3.18 or newer may be required for optimal
functionality.

[Test Plan]
We will follow the QA process from https://documentation.ubuntu.com/sru/en/latest/reference/exception-firmware-updates/:

When a new version of fwupd or fwupdate is uploaded to -proposed, the
following will be done:

    Test that UEFI capsule updates still work properly on an OEM system
pulling from LVFS with secure boot enabled.

    Verify that CI tests have been running for the matching release
upstream.

    Test that a system that offers a variety of in OS devices enumerate
(example Thunderbolt, NVME)

    The appropriate signed packages have been uploaded as well

If all the testing indicates that the image containing the new package
is acceptable, verification will be considered to be done and the the
package can be released from -proposed after the standard aging period.

As for meson-1.5, this is a new package that will solely be used to
build fwupd, so fwupd building is enough of a test plan.

[Where problems could occur]
This is for the OEM team to sort out.

meson-1.5 is a new package and cannot cause any regressions on installed
systems.

[Other info]
These are the most minimal backports of the versions in noble.

A separate bug will be used to track the focal backport (that would land
via esm-infra-updates)

There is a exception for fwupd

https://documentation.ubuntu.com/sru/en/latest/reference/exception-
firmware-updates/

But it only covers updates from the same stable branch, not this update,
which should be evaluated as an individual case.

** Affects: fwupd (Ubuntu)
     Importance: Undecided
         Status: Invalid

** Affects: meson-1.5 (Ubuntu)
     Importance: Undecided
         Status: Invalid

** Affects: fwupd (Ubuntu Jammy)
     Importance: Undecided
         Status: New

** Affects: meson-1.5 (Ubuntu Jammy)
     Importance: Undecided
         Status: New

** Package changed: llvm-toolchain-19 (Ubuntu) => fwupd (Ubuntu)

** Also affects: meson-1.5 (Ubuntu)
   Importance: Undecided
       Status: New

** Also affects: fwupd (Ubuntu Jammy)
   Importance: Undecided
       Status: New

** Also affects: meson-1.5 (Ubuntu Jammy)
   Importance: Undecided
       Status: New

** Description changed:

  [Impact]
  Machines on jammy no longer receive firmware security updates, as the LVFS server seemingly has blocked them because it gates on versions rather than feature flags. While they can presumably install older versions of the firmware, they are unable to get new firmware versions.

  This requires a backport of meson in turn. This bug includes the
  backport of meson-1.5 from the 24.04.2 HWE stack.

  A backport of libxmlb 0.3.18 or newer may be required for optimal
  functionality.

  [Test Plan]
  This is for the OEM team to sort out.

  As for meson-1.5, this is a new package that will solely be used to
  build fwupd, so fwupd building is enough of a test plan.

  [Where problems could occur]
  This is for the OEM team to sort out.

  meson-1.5 is a new package and cannot cause any regressions on installed
  systems.
+ 
+ [Other info]
+ These are the most minimal backports of the versions in noble.

** Changed in: fwupd (Ubuntu)
       Status: New => Invalid

** Changed in: meson-1.5 (Ubuntu)
       Status: New => Invalid

** Description changed:

  [Impact]
- Machines on jammy no longer receive firmware security updates, as the LVFS server seemingly has blocked them because it gates on versions rather than feature flags. While they can presumably install older versions of the firmware, they are unable to get new firmware versions.
+ Machines on jammy no longer receive firmware security updates, as the LVFS server seemingly has blocked the old version. While they can presumably install older versions of the firmware, they are unable to get new firmware versions.

  This requires a backport of meson in turn. This bug includes the
  backport of meson-1.5 from the 24.04.2 HWE stack.

  A backport of libxmlb 0.3.18 or newer may be required for optimal
  functionality.

  [Test Plan]
  This is for the OEM team to sort out.

  As for meson-1.5, this is a new package that will solely be used to
  build fwupd, so fwupd building is enough of a test plan.

  [Where problems could occur]
  This is for the OEM team to sort out.

  meson-1.5 is a new package and cannot cause any regressions on installed
  systems.

  [Other info]
  These are the most minimal backports of the versions in noble.

** Description changed:

  [Impact]
  Machines on jammy no longer receive firmware security updates, as the LVFS server seemingly has blocked the old version. While they can presumably install older versions of the firmware, they are unable to get new firmware versions.

  This requires a backport of meson in turn. This bug includes the
  backport of meson-1.5 from the 24.04.2 HWE stack.

  A backport of libxmlb 0.3.18 or newer may be required for optimal
  functionality.

  [Test Plan]
  This is for the OEM team to sort out.

  As for meson-1.5, this is a new package that will solely be used to
  build fwupd, so fwupd building is enough of a test plan.

  [Where problems could occur]
  This is for the OEM team to sort out.

  meson-1.5 is a new package and cannot cause any regressions on installed
  systems.

  [Other info]
  These are the most minimal backports of the versions in noble.
+ 
+ A separate bug will be used to track the focal backport.

** Description changed:

  [Impact]
  Machines on jammy no longer receive firmware security updates, as the LVFS server seemingly has blocked the old version. While they can presumably install older versions of the firmware, they are unable to get new firmware versions.

  This requires a backport of meson in turn. This bug includes the
  backport of meson-1.5 from the 24.04.2 HWE stack.

  A backport of libxmlb 0.3.18 or newer may be required for optimal
  functionality.

  [Test Plan]
  This is for the OEM team to sort out.

  As for meson-1.5, this is a new package that will solely be used to
  build fwupd, so fwupd building is enough of a test plan.

  [Where problems could occur]
  This is for the OEM team to sort out.

  meson-1.5 is a new package and cannot cause any regressions on installed
  systems.

  [Other info]
  These are the most minimal backports of the versions in noble.

  A separate bug will be used to track the focal backport.
+ 
+ There is a exception for fwupd
+ 
+ https://documentation.ubuntu.com/sru/en/latest/reference/exception-
+ firmware-updates/
+ 
+ But it only covers updates from the same stable branch, not this update,
+ which should be evaluated as an individual case.

** Description changed:

  [Impact]
  Machines on jammy no longer receive firmware security updates, as the LVFS server seemingly has blocked the old version. While they can presumably install older versions of the firmware, they are unable to get new firmware versions.

  This requires a backport of meson in turn. This bug includes the
  backport of meson-1.5 from the 24.04.2 HWE stack.

  A backport of libxmlb 0.3.18 or newer may be required for optimal
  functionality.

  [Test Plan]
  This is for the OEM team to sort out.

  As for meson-1.5, this is a new package that will solely be used to
  build fwupd, so fwupd building is enough of a test plan.

  [Where problems could occur]
  This is for the OEM team to sort out.

  meson-1.5 is a new package and cannot cause any regressions on installed
  systems.

  [Other info]
  These are the most minimal backports of the versions in noble.

- A separate bug will be used to track the focal backport.
+ A separate bug will be used to track the focal backport (that would land
+ via esm-infra-updates)

  There is a exception for fwupd

  https://documentation.ubuntu.com/sru/en/latest/reference/exception-
  firmware-updates/

  But it only covers updates from the same stable branch, not this update,
  which should be evaluated as an individual case.

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

Title:
  Backport fwupd 1.9 to jammy

Status in fwupd package in Ubuntu:
  Invalid
Status in meson-1.5 package in Ubuntu:
  Invalid
Status in fwupd source package in Jammy:
  New
Status in meson-1.5 source package in Jammy:
  New

Bug description:
  [Impact]
  Machines on jammy no longer receive firmware security updates, as the LVFS server seemingly has blocked the old version. While they can presumably install older versions of the firmware, they are unable to get new firmware versions.

  This requires a backport of meson in turn. This bug includes the
  backport of meson-1.5 from the 24.04.2 HWE stack.

  A backport of libxmlb 0.3.18 or newer may be required for optimal
  functionality.

  [Test Plan]
  We will follow the QA process from https://documentation.ubuntu.com/sru/en/latest/reference/exception-firmware-updates/:

  When a new version of fwupd or fwupdate is uploaded to -proposed, the
  following will be done:

      Test that UEFI capsule updates still work properly on an OEM
  system pulling from LVFS with secure boot enabled.

      Verify that CI tests have been running for the matching release
  upstream.

      Test that a system that offers a variety of in OS devices
  enumerate (example Thunderbolt, NVME)

      The appropriate signed packages have been uploaded as well

  If all the testing indicates that the image containing the new package
  is acceptable, verification will be considered to be done and the the
  package can be released from -proposed after the standard aging
  period.

  As for meson-1.5, this is a new package that will solely be used to
  build fwupd, so fwupd building is enough of a test plan.

  [Where problems could occur]
  This is for the OEM team to sort out.

  meson-1.5 is a new package and cannot cause any regressions on
  installed systems.

  [Other info]
  These are the most minimal backports of the versions in noble.

  A separate bug will be used to track the focal backport (that would
  land via esm-infra-updates)

  There is a exception for fwupd

  https://documentation.ubuntu.com/sru/en/latest/reference/exception-
  firmware-updates/

  But it only covers updates from the same stable branch, not this
  update, which should be evaluated as an individual case.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/2116176/+subscriptions