Tuesday, 10 November 2015

Re: ANN: autopkgtests are now specific for "triggering" package for better isolation

On Tue, Nov 10, 2015 at 5:55 AM, Martin Pitt <[email protected]> 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


This works because locally-installed packages have a pin of 100, so by
default the packages pinned to 50 won't be chosen over what's already
installed, unless a package in the ppa pinned at 1100 has a versioned
dependency that's only satisfiable by a package that's pinned to 50.

As a guess if you're working with proposed instead of PPAs you'd want
a pin like this:

Package: *
Pin: release a=$SERIES-proposed
Pin-Priority: 1100

Package: *
Pin: release a=$SERIES*
Pin-Priority: 50


HTH

--
ubuntu-devel mailing list
[email protected]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel