[Bug 1317054] [NEW] no_proxy preseeding not supported

[Colin Watson]

Public bug reported:

Hi all,

I've hunted high and low for the answer to this question, through every
document I can think of on the topic, and through the debian-installer
sources (on Debian's anonscm.debian.org site no less) for the answer to
this.

We have a exterior proxy server running apt-cacher-ng which we use for
fetching package updates for all systems including the ones in the DMZ.
We preseed this in the Ubuntu installation like so:

d-i mirror/http/proxy string http://apt-cache.our.domain:3142

So far so good.

We also have some corporate APT repositories for some in-house packages.
These are *NOT* accessible to the DMZ, and I'd rather not have to funnel
requests through a second apt-cacher-ng instance that can access these
internal repositories.

APT itself has a provision for this:
Acquire::http::Proxy "http://apt-cache.my.domain:3142";
Acquire::http::Proxy::secret-apt-repo.my.domain DIRECT;

There's also the old fashioned no_proxy environment variable, which apt
respects along with http_proxy (which debian-installer sets).

I don't see any mention anywhere of a mirror/http/no_proxy… where do I
set this configuration parameter?

Regards,
Stuart Longland

** Affects: apt-setup (Ubuntu)
     Importance: Wishlist
         Status: Triaged

** Package changed: debian-installer (Ubuntu) => apt-setup (Ubuntu)

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

Title:
  no_proxy preseeding not supported

Status in “apt-setup” package in Ubuntu:
  Triaged

Bug description:
  Hi all,

  I've hunted high and low for the answer to this question, through
  every document I can think of on the topic, and through the debian-
  installer sources (on Debian's anonscm.debian.org site no less) for
  the answer to this.

  We have a exterior proxy server running apt-cacher-ng which we use for
  fetching package updates for all systems including the ones in the
  DMZ.  We preseed this in the Ubuntu installation like so:

  d-i mirror/http/proxy string http://apt-cache.our.domain:3142

  So far so good.

  We also have some corporate APT repositories for some in-house
  packages.  These are *NOT* accessible to the DMZ, and I'd rather not
  have to funnel requests through a second apt-cacher-ng instance that
  can access these internal repositories.

  APT itself has a provision for this:
  Acquire::http::Proxy "http://apt-cache.my.domain:3142";
  Acquire::http::Proxy::secret-apt-repo.my.domain DIRECT;

  There's also the old fashioned no_proxy environment variable, which
  apt respects along with http_proxy (which debian-installer sets).

  I don't see any mention anywhere of a mirror/http/no_proxy… where do I
  set this configuration parameter?

  Regards,
  Stuart Longland

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt-setup/+bug/1317054/+subscriptions