debcrafters-packages team mailing list archive

[Launchpad Bug Tracker <2115633@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package lvm2 - 2.03.31-2ubuntu1

---------------
lvm2 (2.03.31-2ubuntu1) questing; urgency=medium

  * Merge with Debian unstable (LP: #2115633). Remaining changes:
    - d/.gitignore deleted
    - d/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
    - d/lvm2.initramfs-hook
      depend on udev since we ship udev rules
    - d/control and d/rules do not build udeb target
    - d/rules
      + Copy .po file to .pot file for Rosetta (Ubuntu specific)
    - d/control
      + add thin-provisioning-tools build-dep as configure wants it
        around for some checks at build time.
      + 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)
    - d/patches
      + 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)
      + 0014-no-lvm2-monitor-in-containers.patch:
        Do not start lvm2-monitor in containers (LP #1576341)

lvm2 (2.03.31-2) unstable; urgency=medium

  * Ask build system to install stuff writable. (closes: #1104357)

lvm2 (2.03.31-1) unstable; urgency=medium

  * New upstream release.

  [ Luke W Faraone ]
  * Include lvresize_fs_helper (Closes: #1068733)

 -- John Chittum <john.chittum@xxxxxxxxxxxxx>  Wed, 25 Jun 2025 13:59:23
-0400

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

-- 
You received this bug notification because you are a member of
Debcrafters packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/2115633

Title:
  lvm 2.03.31-1 marked as latest in Debian Publishing history breaking
  git-ubuntu workflows

Status in git-ubuntu:
  New
Status in lvm2 package in Ubuntu:
  Fix Released

Bug description:
  lvm2 is currently at 2.03.31-2 in Debian testing, published on
  2025-05-05. Something(TM) happened on 2025-05-15 that caused lvm2
  2.03.31-1 to be re-listed as the latest published version in
  Debian.[0] There's nothing in the Debian Tracker that suggest its on
  their side[0].

  Please reset the Debian publishing history in Launchpad to match the
  state in Debian. This is currently breaking git-ubuntu "default"
  workflows, as it marks debian/sid & new/debian as 2.03.31-1

  [0] https://launchpad.net/debian/+source/lvm2/+publishinghistory
  [1] https://tracker.debian.org/pkg/lvm2

  UPDATE: TIL that a previous Debian source can be made available to
  fulfill Built-Using. 2.03.31-1 is source available in debian/sid to
  fulfill Built-Using. Something picked that change up and set
  debian/sid to that version. git-ubuntu is unable to deal with the rare
  situation of multiple source package versions being available in a
  Suite, something that is supported and clients need to be able to
  tolerate.

To manage notifications about this bug go to:
https://bugs.launchpad.net/git-ubuntu/+bug/2115633/+subscriptions