automatically setup proxies other than apt-cacher-ng

Bug #1577966 reported by Martin Pitt
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
autopkgtest (Ubuntu)
Fix Released
Undecided
Martin Pitt

Bug Description

setup-testbed, adt-build-lx[cd] and adt-buildvm-ubuntu-cloud currently hardcode the apt-cacher-ng port 3142. There is no real reason to do that, it should use any other port (for different proxies) too.

Martin Pitt (pitti)
Changed in autopkgtest (Ubuntu):
status: New → Triaged
assignee: nobody → Martin Pitt (pitti)
Revision history for this message
Martin Pitt (pitti) wrote :
Changed in autopkgtest (Ubuntu):
status: Triaged → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package autopkgtest - 3.20.6

---------------
autopkgtest (3.20.6) unstable; urgency=medium

  * Fix OSError when running a shell is requested but /dev/tty does not exist;
    just log an error instead.
  * Fix parsing of candidate versions from "apt-cache policy" to always use
    the precise given package name. By default it falls back to a
    substring/regexp search (undocumented).
  * adt-build-lxd: Check the LXD configuration for the LXD bridge instead of
    the old LXC bridge, for apt proxy auto-detection. (LP: #1577968)
  * Generalize the apt proxy detection in adt-build* and setup-testbed to
    work for arbitrary proxies, not just apt-cacher-ng. (LP: #1577966)
  * Eliminate the need to set $AUTOPKGTEST_BASE to execute runner/adt-run from
    a git checkout. This also makes ./run-from-checkout obsolete, call
    runner/adt-run directly.

 -- Martin Pitt <email address hidden> Tue, 17 May 2016 22:32:46 +0200

Changed in autopkgtest (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.