add-apt-repository should look at apt.conf for proxy

[joopbraak]

At the moment add-apt-repository doesn't work behind a proxy.

The workaround in bug #516032 should not be necessary and is not a fix.
add-apt-repository should just look at the proxy configuration in /etc/apt/apt.conf.
https is necessary for checking the ppa and http for adding the key.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Martin Pool (mbp)]

joopbraak, please mark dupes onto the oldest or most complete report, not the newest one.

[joopbraak (joopbraak)]

OK, sorry, but I thought that bug was only about the gpg part of add-apt-repository (and I thought my description of the problem was clearer). In my situation add-apt-repository already halts before that, not being able to contact the ppa through https because it ignores the proxy settings.

[joopbraak (joopbraak)]

Also if it takes the proxy settings from apt.conf it's not dependent of environmental settings of the root account, it can use these proxy settings to contact the ppa and use gpg with "--keyserver-options http-proxy=value".

[joopbraak (joopbraak)]

The gpg option "--keyserver-options honor-http-proxy" doesn't seem to exist anymore.

[joopbraak (joopbraak)]

Just tell me what kind of diagnostic information you need from me to solve this.
What I noticed so far is that when I only open port 443 on my firewall it would get through the first part but get stuck at gpg, when only opening port 80 it would get stuck immediately (not being able to contact the ppa through https to get the necessary data).
Only when opening port 80 and 443 there were no errors.

So both http and https proxy settings are needed for it to work (when port 80 and 443 are closed).

I don't know yet if https_proxy should be https://www.example.com:8000/ or http://www.example.com:8000/