[Bug 1060900] Re: HTTP proxy config being created in /etc/apt/apt.conf on nodes

Robie Basak 1060900 at bugs.launchpad.net
Sun Oct 21 10:58:53 UTC 2012


Thanks for the explanation Ryan!

I feel that there must be a better way, such as the apt proxy working
with non-standard apt sources without issues. But wanting to disable any
existing apt proxy in a charm does make sense.

What if debian-installer were changed to always use
/etc/apt/apt.conf.d/10proxy? Although there would still be no guarantee
if that file doesn't exist that there is no proxy configured some other
way, and the same charm might conceivably run on some other service
provider's cloud instance with a proxy set in some other way.

Changing this task to debian-installer for consideration nevertheless.

But we should have a separate upstream MAAS bug to add a configurable
proxy. You mentioned existing bugs, but I can't find one. Do you have a
bug number, or shall we create a separate bug if not?

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

** Summary changed:

- HTTP proxy config being created in /etc/apt/apt.conf on nodes
+ d-i should use apt.conf.d instead of adding proxy to apt.conf directly

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

Title:
  d-i should use apt.conf.d instead of adding proxy to apt.conf directly

Status in “debian-installer” package in Ubuntu:
  New

Bug description:
  When deploying a node, /etc/apt/apt.conf is being created with, for
  example:

  Acquire::http::Proxy "http://10.55.65.6:8000/";

  Please instead deploy this in, say, /etc/apt/apt.conf.d/90maas.

  Version: precise 0.1+bzr482+dfsg-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1060900/+subscriptions




More information about the foundations-bugs mailing list