selective sync from debian: haproxy case

[Colin Watson]

I have no real opinion on the main question, but on a question of fact:

On Mon, Dec 02, 2019 at 04:52:08PM -0300, Andreas Hasenack wrote:
> On Mon, Dec 2, 2019 at 3:35 PM Steve Langasek <steve.langasek at ubuntu.com> wrote:
> > What about using a block-proposed bug on the package instead?
> 
> Hm, let's see how that would work.
> 
> I file a bug saying this package shouldn't be synced automatically
> (for example), and add that tag. Then each time there is a debian
> update, it will not migrate, and I will check if that update is one I
> want to have.
> If yes, I remove the tag, let it migrate, and add the tag back again.
> If not, I leave it as is, or perhaps ask someone from the release team
> to remove it from proposed? Won't it just be synced again then?

You'd likely want it removed from -proposed in that case so that it's
possible to upload new versions.  It wouldn't be auto-synced unless a
newer version is then uploaded to Debian unstable.

It might be worth somebody investigating beefing up auto-sync to support
"block-auto-sync" bugs on packages for this sort of situation.

-- 
Colin Watson                                       [cjwatson at ubuntu.com]