debcrafters-packages team mailing list archive

[John Chittum <2115633@xxxxxxxxxxxxxxxxxx>]

git-ubuntu is setting `debian/sid` as `2.03.31-1`, probably because it
sees the latest publication as that version. git-ubuntu seems unable to
deal with multiple package versions in any given $SUITE.

apt and dpkg can definitely handle the idea of multiple versions
available, and there are ways in Ubuntu to allow it, but by default, no
Ubuntu does not generally tolerate multiple versions of packages. Ubuntu
doesn't provide `Build-Using` (unless i'm mistaken) and I'm not sure we
allow for the same situation -- a previous version of a package being
source available because current packages have built against it. The
normal move would be a transition, and rebuild of the packages requiring
it.

So...interesting "next step" on our side, as I'm definitely in
unfamiliar territory. Can certainly look at patching `git-ubuntu` to
handle more complex situations, but I'll need to think on it more. for
this exact issue, I can work around it locally by

* checkout pkg/import/2.03.31-2
* checkout -b debian/2.03.31-2
* rebase against merge against local branch
* push both branches
* do MP of merge against debian/2.03.31-2 to show the relevant diff

since the MP is informative, that should work. But I'm not sure how to
deal with the situation for future cases.

** Also affects: git-ubuntu
   Importance: Undecided
       Status: New

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

** Summary changed:

- remove lvm 2.03.31-1 as latest in Debian Publishing history
+ lvm 2.03.31-1 marked as latest in Debian Publishing history breaking git-ubuntu workflows

** Description changed:

  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.

-- 
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:
  Invalid

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