Hi Andreas,
On Mon, Dec 02, 2019 at 03:03:01PM -0300, Andreas Hasenack wrote:
> Hi all,
>
> haproxy is currently a sync in ubuntu, at version 2.0.10-1. The 2.0.x
> line is upstream's stable LTS line, and I would like to stay there.
>
> Debian experimental already has 2.1.0-2, which is also an upstream
> stable line, but not an LTS.
>
> I would prefer that we don't move to 2.1.0 for the next ubuntu LTS
> version, so how would I go about preventing that from being synced
> into Ubuntu should debian move 2.1.0 from experimental to unstable? I
> would like to continue to receive updates from unstable as long as
> it's tracking the 2.0.x upstream line.
> Some options I heard about:
> a) sync blacklist
> (https://bazaar.launchpad.net/~ubuntu-archive/+junk/sync-blacklist/view/head:/sync-blacklist.txt)
> b) add an ubuntu version to the package, even though it's identical to
> the debian one
> Any other options?
I wouldn't recommend using the sync blacklist, since it's not self-service
(~ubuntu-archive) and it also blocks you from doing manual syncs using the
standard tools (syncpackage).
Setting a fake Ubuntu version seems doable, and managing the flow of new
versions as merges, if a bit ugly.
What about using a block-proposed bug on the package instead?
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer https://www.debian.org/
slangasek@ubuntu.com vorlon@debian.org
