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

Steve Langasek steve.langasek at canonical.com
Tue Oct 13 18:27:08 UTC 2015


The issue here is that libobrender32 is a new library in wily-proposed,
but libobt2 is an existing library in wily and libobrender32 needs the
newer version of the library from wily-proposed.  That falls under the
'caveat' in my analysis.

Perhaps in this case we should fall back to installing with no pins, at
least as a first approximation?

-- 
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



More information about the foundations-bugs mailing list