debcrafters-packages team mailing list archive
-
debcrafters-packages team
-
Mailing list archive
-
Message #03022
[Bug 2115633] Re: lvm 2.03.31-1 marked as latest in Debian Publishing history breaking git-ubuntu workflows
Built-Using is a field where we record precise versions of things that
are linked within a binary whose sources still need to be available for
license compliance reason. Presumably we *should* be doing the same
thing as Debian in terms of keeping sources available if in Built-Using?
Although one could argue that it's already available through LP...
I'm with Colin on the g-u behaviour, it feels like a bug here. Your
workaround if fine, as long as we're using the proper Debian tag and
it's spelled out in the MP it should all work out.
--
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
References