On 17:10 Fri 23 May , Ghislain wrote: > Le 23/05/2014 15:23, Baptiste a écrit : > >It is not provided by us (HAProxy.com) if this is what you mean. > > > >Baptiste > > > > > > yes that's what i meant. Thanks for both answer and thanks for the product, > and the packages ! > > In any case from my high throne in the sky looking under at other petty > humans i will consider worthy of my trust the debian team, amen ;p
Thanks :) > Now that we have cleared this, that raise another question as i may been a > little paranoid as most sysadmin should be so , do you think this: > > /etc/apt/preferences.d/haproxy > > Package: haproxy > Pin: origin haproxy.debian.net, version 1.5* > Pin-Priority: 995 > > Package: * > Pin: origin haproxy.debian.net > Pin-Priority: -10 > > will make sure this repository can never ever touch anything else than the > 'haproxy' package ? I think the Pin: line of the first entry is not valid, the following should work: Package: haproxy Pin: version 1.5* Pin: origin haproxy.debian.net Pin-Priority: 777 Package: * Pin: origin haproxy.debian.net Pin-Priority: -10 You can always check the result using `apt-cache policy haproxy'. You should also allow haproxy-dbg. > > i start to have a repository per process those days if i do not limit > those > a little they will one day come to bite me ! Another option would be to setup your own local repository using e.g. reprepro and import only the packages generated from the "haproxy" source. This is what I've been using at work to control a lot of upstream repositories and stage packages when/if we want to. Note that this repository is only a temporary solution, until 1.5-final is out. Then we will upload it to unstable and wheezy-backports proper. Regards, Apollon
