On Tue, Nov 10, 2015 at 09:12:25AM -0800, Robert Park wrote:
> On Tue, Nov 10, 2015 at 5:55 AM, Martin Pitt <martin.pitt@ubuntu.com> wrote:
> > Note that apt pinning is rather limited. Unfortunately you can't say
> > "from -proposed use these packages and any of their dependencies which
> > are not satisfiable in -release" -- pinning is not clever enough for
> > that.
> Are you sure about that? That sounds like exactly what I just did with
> the citrain tool, I set the pins so that packages from the silo PPA
> can be upgraded, but upgrades from -release pocket and overlay PPA are
> only brought in if explicitly depended upon by packages in the silo
> PPA.
> The pin looked like this:
> Package: *
> Pin: release o=*$PPA_NAME*
> Pin-Priority: 1100
> Package: *
> Pin: release a=$SERIES*
> Pin-Priority: 50
That works for a silo, because with a silo you want to install *all* of the
packages from the ppa together, and pull any additional dependencies from
the main archive. For -proposed, we explicitly want to pick and choose
*which* packages we are pulling from -proposed vs. the release pocket,
because -proposed always contains multiple unrelated "landings" at the same
time and we want to be able to disambiguate the test results so we know
which package introduces the regression.
--
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 http://www.debian.org/
slangasek@ubuntu.com vorlon@debian.org
