← Back to team overview

canonical-ubuntu-qa team mailing list archive

[Bug 2009191] Re: autopkgtest: Specifying --apt-pocket causes wrong unwanted pinning to default release

 

The ingredients required to hit this bug are:

1. an all-proposed build (--apt-pocket=proposed with no package pinning)
2. multiple tests defined in d/t/control
3. the tests do not allow reusing the same testbed system

Condition 1. means that we don't hit the bug in tests runs triggered
by britney, as those are not all-proposed.

** Changed in: autopkgtest (Ubuntu)
     Assignee: (unassigned) => Paride Legovini (paride)

** Changed in: autopkgtest (Ubuntu)
       Status: New => In Progress

-- 
You received this bug notification because you are a member of
Canonical's Ubuntu QA, which is subscribed to autopkgtest in Ubuntu.
https://bugs.launchpad.net/bugs/2009191

Title:
  autopkgtest: Specifying --apt-pocket causes wrong unwanted pinning to
  default release

Status in autopkgtest package in Ubuntu:
  In Progress
Status in autopkgtest package in Debian:
  New

Bug description:
  Imported from Debian bug http://bugs.debian.org/1032314:

  Package: autopkgtest
  Severity: normal
  X-Debbugs-Cc: paride@xxxxxxxxxx

  Adding a pocket via --apt-pocket=<POCKET> causes the
  _get_default_release() function to be called. This is needed to
  construct the sources.list entry for the pocket, which will be in the
  form of:

    deb <mirror> <default_release>-<POCKET> ...

  The _get_default_release() function caches the detected default
  release in the default_release variable, which is the same variable
  used to store the --apt-default-release=<RELEASE> value. This has
  no effect when only one test is present in d/t/control, but when
  more than one test is present the tests after the first will have
  unwanted/wrong pinning (as if --apt-default-release was specified).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/2009191/+subscriptions



References