[Bug 1503150] Re: Minimize installed packages from -proposed

[Martin Pitt]

@Steve: I just tried this on current wily-proposed with
http://people.canonical.com/~ubuntu-archive/proposed-
migration/update_excuses.html#obconf :

---- /etc/apt/preferences.d/01autopkgtest ----
Package: obconf
Pin: release a=wily-proposed
Pin-Priority: 900

Package: *
Pin: release a=wily
Pin-Priority: 900

Package: *
Pin: release a=wily-proposed
Pin-Priority: 100
------------------------------------------------------------

# apt-get install -s obconf
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 obconf : Depends: libobrender32 (>= 3.6.0) but it is not going to be installed
          Depends: libobt2 (>= 3.6.0) but 3.5.2-8 is to be installed
          Recommends: openbox but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

It seems it's not considering its dependencies from -proposed, but tries
to install everything else from wily? Only if I bump the priority in the
third clause from 100 to 900 it works again (but then of course installs
all deps from -proposed).

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to autopkgtest in Ubuntu.
https://bugs.launchpad.net/bugs/1503150

Title:
  Minimize installed packages from -proposed

Status in Auto Package Testing:
  Triaged
Status in britney:
  Confirmed
Status in autopkgtest package in Ubuntu:
  In Progress

Bug description:
  It sometimes happens that a package P in -proposed gets stuck because
  one of its dependencies D also gets uploaded and is broken. Right now
  we always run all tests against the entirety of -proposed, which will
  cause P's tests to  fail due to the broken D.

  However, in many cases P's dependencies will be satisfiable in
  -release, so if we would run tests only against P's -proposed binaries
  and only use those packages from -proposed which are necessary to
  satisfy the dependencies (to catch library transitions or packages
  with versioned Depends: which need to land in lockstep) we could land
  P and still keep D in -proposed.

  This needs fleshing out, and we need to figure out how to do that with
  apt pinning.

  Once we do that, we need to become strict in britney about always
  respecting the recorded triggering package in the result logs. We must
  then not consider newer test results which were run against a
  different trigger Q as an updated test result for a failing test
  against P. We currently only do this results-per-trigger tracking for
  kernels, but not for normal packages as the triggering package
  currently doesn't influence the test results there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/auto-package-testing/+bug/1503150/+subscriptions