Re: pybuild and proxies -- could we make prohibition optional?

2015-07-27 Thread Piotr Ożarowski
I already followed Dimitri's suggestion to add no_proxy=localhost and will add your PYBUILD_FAKE_PROXY later today awesome! feel free to tune the name to whatever you feel more appropriate. I simply do not forward empty http{,s}_proxy, is that good enough?

Re: pybuild and proxies -- could we make prohibition optional?

2015-07-27 Thread Dimitri John Ledkov
On 27 July 2015 at 21:31, Piotr Ożarowski pi...@debian.org wrote: I already followed Dimitri's suggestion to add no_proxy=localhost and will add your PYBUILD_FAKE_PROXY later today awesome! feel free to tune the name to whatever you feel more appropriate. I simply do not forward empty

Re: pybuild and proxies -- could we make prohibition optional?

2015-07-22 Thread Piotr Ożarowski
[Yaroslav Halchenko, 2015-07-21] As I have mentioned some tools might not be smart about empty values in http_proxy, try e.g. git-annex under such settings ah, sorry, I only quickly scanned you email. I already followed Dimitri's suggestion to add no_proxy=localhost and will add your

Re: pybuild and proxies -- could we make prohibition optional?

2015-07-22 Thread Ansgar Burchardt
On 07/21/2015 10:21 PM, Dimitri John Ledkov wrote: In practice however we do allow accessing debian ftp archive and localhost services, thus: no_proxy=localhost,*.debian.org would probably be better imho for the balance of don't allow general network access, yet allow sensible networking

Re: pybuild and proxies -- could we make prohibition optional?

2015-07-22 Thread Yaroslav Halchenko
On Wed, 22 Jul 2015, Piotr Ożarowski wrote: [Yaroslav Halchenko, 2015-07-21] As I have mentioned some tools might not be smart about empty values in http_proxy, try e.g. git-annex under such settings ah, sorry, I only quickly scanned you email. I already followed Dimitri's suggestion

Re: pybuild and proxies -- could we make prohibition optional?

2015-07-22 Thread Daniel Stender
On 22.07.2015 15:45, Yaroslav Halchenko wrote: On Wed, 22 Jul 2015, Piotr Ożarowski wrote: [Yaroslav Halchenko, 2015-07-21] As I have mentioned some tools might not be smart about empty values in http_proxy, try e.g. git-annex under such settings ah, sorry, I only quickly scanned you

pybuild and proxies -- could we make prohibition optional?

2015-07-21 Thread Yaroslav Halchenko
talking about this ;-) : $ grep -A3 http_proxy pybuild if 'http_proxy' not in env: env['http_proxy'] = 'http://127.0.0.1:9/' if 'https_proxy' not in env: env['https_proxy'] = 'https://127.0.0.1:9/' which is overall GREAT since now I can drop off all those manual

Re: pybuild and proxies -- could we make prohibition optional?

2015-07-21 Thread Dimitri John Ledkov
On 21 July 2015 at 20:17, Yaroslav Halchenko deb...@onerussian.com wrote: talking about this ;-) : $ grep -A3 http_proxy pybuild if 'http_proxy' not in env: env['http_proxy'] = 'http://127.0.0.1:9/' if 'https_proxy' not in env: env['https_proxy'] =

Re: pybuild and proxies -- could we make prohibition optional?

2015-07-21 Thread Yaroslav Halchenko
As I have mentioned some tools might not be smart about empty values in http_proxy, try e.g. git-annex under such settings On July 21, 2015 4:16:11 PM EDT, Piotr Ożarowski pi...@debian.org wrote: So, long story short... would it be ok if I propose/commit a change like no need, if you want to

Re: pybuild and proxies -- could we make prohibition optional?

2015-07-21 Thread Piotr Ożarowski
So, long story short... would it be ok if I propose/commit a change like no need, if you want to disable it, just set https_proxy to empty string f.e. if you want to enable it only in tests: override_dh_auto_test: http_proxy='' dh_auto_test -- Piotr Ożarowski