This bug was fixed in the package lvm2 - 2.03.16-3ubuntu1

lvm2 (2.03.16-3ubuntu1) noble; urgency=medium

  * Merge from Debian unstable (LP: #2054683). Remaining changes:
    - Lower libdevmapper1.02.1's Depends: dmsetup to a Recommends:. This
      breaks the circular dependency that causes upgrade failures. As dmsetup
      is "Priority: required", this has no other practical consequences.
      (Debian #586424)
    - Add debian/initramfs-tools/lvm2/scripts/init-bottom/lvm2: We cannot
      properly synthesize LVM LV change events with udevadm trigger, so if we
      use LVM, we need to let it finish; otherwise we get missing LV symlinks.
    - Add enable-issue-discards.patch: Enable "issue_discards" option by
      default to trim SSDs when changing PVs. This option has no effect if the
      kernel or the drive does not support trimming, so it's safe to enable by
      default. (Debian #717313)
    - debian/rules:
      - Copy .po file to .pot file for Rosetta (Ubuntu specific).
    - debian/initramfs-tools/lvm2/hooks/lvm2: depend on udev since we ship
      udev rules.
    - Do not start lvm2-monitor in containers (LP #1576341)
    - Fix patch of systemd-run in 69-lvm-metad.rules
    - d/control: add thin-provisioning-tools build-dep as configure wants it
      around for some checks at build time.
    - Don't build udeb targets.

lvm2 (2.03.16-3) unstable; urgency=medium

  * Remove obsolete dependency on lsb-base.
  * Expect systemd relates files in /usr. (closes: #1052666)
  * Move all remaining files to /usr.

 -- Dave Jones <>  Thu, 22 Feb 2024 10:28:18

** Changed in: lvm2 (Ubuntu)
       Status: In Progress => Fix Released

You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.

  Please merge lvm2 2.03.16-3 from Debian unstable.

Status in lvm2 package in Ubuntu:
  Fix Released

Bug description:
  Please merge lvm2 2.03.16-3 from Debian unstable.

  Updated changelog and diff against Debian unstable to be attached

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to