debcrafters-packages team mailing list archive

[John Chittum <2115633@xxxxxxxxxxxxxxxxxx>]

in discussions with the archive-admins, since the issue is not an Ubuntu
source, they do not feel empowered to make this change. Chat was held in
devel:ubuntu.com matrix server.

John Chittum
archive-admin fun -- lvm2 somehow got synced incorrectly into lp debian history: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/2115633

ginggs
I added this to the agenda for the ubuntu-archive meeting, which will happen in about an hour

ginggs
John Chittum the consensus was these versions are not in the Ubuntu Archive, so ubuntu-archive have no powers to act on them

John Chittum
so falls back to Launchpad team?

Yes

-- 
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:
  remove lvm 2.03.31-1 as latest in Debian Publishing history

Status in lvm2 package in Ubuntu:
  New

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

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