gpg doesn't see the mandatory http proxy

[Martin Pool]

There are a few cases like bug 712666 and bug 710054 where users seem to need an http proxy, and they have it set up well enough that they can get to Launchpad, but it's not configured into gpg.

Many users will not have used gpg before, and they probably haven't configured it, and I don't think it reads the standard $http_proxy etc. So they get fairly cryptic failures as in those bugs.

I can think of a few things we could do:

 * read the key over http ourselves, and feed it into gpg
 * always pass --keyserver-options honor-http-proxy
 * determine the proxy we think is best and explicitly pass that

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: python-software-properties 0.76.7
ProcVersionSignature: Ubuntu 2.6.35-25.44-generic 2.6.35.10
Uname: Linux 2.6.35-25-generic x86_64
Architecture: amd64
Date: Fri Feb 4 10:02:35 2011
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, user)
 LANG=en_AU.utf8
 SHELL=/bin/zsh
SourcePackage: software-properties

[Martin Pool (mbp)]

Actually to judge by <http://manpages.ubuntu.com/manpages/maverick/en/man1/gpg.1.html> gpg now always honors the $http_proxy variable if it's set. However, it might not be set for these users, or sudo might be stripping it from the environment.

[Martin Pool (mbp)]

We may also have to set https_proxy; this is close to a dupe of bug 443404.