janakaravi: please don't assign yourself to bugs unless you plan to work on them and provide a patch for the issue.
Looks to me like add-apt-repository works just fine behind even a very restrictive proxy; however there is a catch (but not something that can be worked around in code, or that should be worked around in code).
add-apt-repository itself requires the https_proxy variable to be able to access Launchpad and get information about the PPAs, such as their descriptions, signing key, etc.
However, the *http_proxy* variable is also required, because that's what gets used by apt-key/gpg to retrieve the GPG keys signing the PPA packages.
I'll mark this as Fix Released for Quantal since it's clearly working properly; and open a task for Precise set to Incomplete until I or the original reporter can re-test on Precise with http_proxy set.
It's possible any other issues may come from sudo clearing some environment variables it shouldn't, but that should already have been fixed in Quantal and Precise.
janakaravi: please don't assign yourself to bugs unless you plan to work on them and provide a patch for the issue.
Looks to me like add-apt-repository works just fine behind even a very restrictive proxy; however there is a catch (but not something that can be worked around in code, or that should be worked around in code).
add-apt-repository itself requires the https_proxy variable to be able to access Launchpad and get information about the PPAs, such as their descriptions, signing key, etc.
However, the *http_proxy* variable is also required, because that's what gets used by apt-key/gpg to retrieve the GPG keys signing the PPA packages.
I'll mark this as Fix Released for Quantal since it's clearly working properly; and open a task for Precise set to Incomplete until I or the original reporter can re-test on Precise with http_proxy set.
It's possible any other issues may come from sudo clearing some environment variables it shouldn't, but that should already have been fixed in Quantal and Precise.