> Johan Walles writes:
> I think I found it.
> My NO_PROXY environment variable had a list of hosts ending in ",":
hmpf
Well done !
> jo...@transwarp:/tmp/bzr-2.1.1$ echo $NO_PROXY
>
localhost,127.0.0.0/8,*.local,*.oracle.com,*.oraclecorp.com,infraworklist,wiki,trat,tendri
I think I found it.
My NO_PROXY environment variable had a list of hosts ending in ",":
jo...@transwarp:/tmp/bzr-2.1.1$ echo $NO_PROXY
localhost,127.0.0.0/8,*.local,*.oracle.com,*.oraclecorp.com,infraworklist,wiki,trat,tendril,infradb01,bkstage,*.jrpg.bea.com,*.bea.com,reporting,qareport,devporta
No, we can't edit the comments so I suppose marking it private is the
only alternative :-/
So, if unsetting the no_proxy variable doesn't work, the last resort is that
python's urllib.proxy_bypass() is
telling us to avoid the proxy for bzr.savannah.gnu.org ? That sounds quite
suspicious and hard
Marking as private because of list of private hosts.
Editing them out of comment 15 would probably work as well but I don't
think that's possible for me.
--
Bzr 2.1.1 broken through HTTP proxy
https://bugs.launchpad.net/bugs/586341
You received this bug notification because you are a member of U
** Visibility changed to: Private
--
Bzr 2.1.1 broken through HTTP proxy
https://bugs.launchpad.net/bugs/586341
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu
jo...@transwarp:/tmp$ echo $all_proxy
socks://www-proxy.se.oracle.com:80/
jo...@transwarp:/tmp$ echo $no_proxy
localhost,127.0.0.0/8,*.local,*.oracle.com,*.oraclecorp.com,infraworklist,wiki,trat,tendril,infradb01,bkstage,*.jrpg.bea.com,*.bea.com,reporting,qareport,devportal,monitor,
Unsetting bot
Thanks for the detailed feedback.
So, AFAICT from these output, the proxy variables are not seen and bzr
try to connect to
0.105 * About to connect() to bzr.savannah.gnu.org:80
yet,
Will bind http_request for 'http://www-proxy.se.oracle.com:80/'
Will bind http_request for 'https://www-pr
** Attachment added: "~/.bzr.log from running with DEBUG=3 in
_urllib2_wrappers.py"
http://launchpadlibrarian.net/49482846/bzr-debug3.log
--
Bzr 2.1.1 broken through HTTP proxy
https://bugs.launchpad.net/bugs/586341
You received this bug notification because you are a member of Ubuntu
Bugs,
I downloaded the bzr-2.1.1 source code and reproduced the error using DEBUG=3
as requested and these instructions:
http://wiki.bazaar.canonical.com/InstallationFaq#RunFromSourceDirectory
** Attachment added: "Console output running with DEBUG=3 in
_urllib2_wrappers.py"
http://launchpadlibrar
Huh ?
bzr checks the *_proxy environment variables to decide whether a proxy should
be used...
...
urgh, of course the proxy handling tracing doesn't use -Dhttp :-(
Since we don't connect, -Dhttp can't output anything (the 'About to
connect' lines are unconditional).
Hmm, that needs to be fi
Here's the .bzr.log after running with -Dhttp.
I don't see anything about any proxy in there; how does bzr detect it
should go via a proxy?
Regards /J
** Attachment added: ".bzr.log with -Dhttp"
http://launchpadlibrarian.net/49437462/.bzr.log
--
Bzr 2.1.1 broken through HTTP proxy
https:/
Oh, and be sure to inspect these headers for auth info, we don't need them (we
just need to make sure they are present when needed) but they may contain
sensitive data (like poorly encrypted user/passwords), look for
'Authorization' headers in particular.
--
Bzr 2.1.1 broken through HTTP proxy
Sorry. I've been unclear.
What we need here is the relevant part of ~/.bzr.log as -Dhttp dumps the
headers for all the requests there
and that's where I expect to get relevant information to diagnose the problem.
--
Bzr 2.1.1 broken through HTTP proxy
https://bugs.launchpad.net/bugs/586341
You
Yes, the proxy is correctly configured :-). Curl works for example:
jo...@transwarp:/tmp/ech$ curl http://ftp.sunet.se/pub/FreeBSD/CERT/README | wc
-l
% Total% Received % Xferd Average Speed TimeTime Time Current
Dload Upload Total Spen
> Can you get a backtrace for it please - run bzr with -Derror.
and -Dhttp
--
Bzr 2.1.1 broken through HTTP proxy
https://bugs.launchpad.net/bugs/586341
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Johan Walles wrote:
> Here's the output I get from running bzr branch -Derror
> http://bzr.savannah.gnu.org/r/gnash.
>
> ** Attachment added: "bzr branch -Derror http://bzr.savannah.gnu.org/r/gnash";
>http://launchpadlibrarian.net/49257319/Derror.
I got different output in different runs. Here's the first run, it was
done with a Swedish locale and the error message...
[Errno 110] Förbindelsen dog ut (timeout)
... means...
[Errno 110] The connection timed out (timeout)
** Attachment added: "Another output from bzr branch -Derror
http:/
Here's the output I get from running bzr branch -Derror
http://bzr.savannah.gnu.org/r/gnash.
** Attachment added: "bzr branch -Derror http://bzr.savannah.gnu.org/r/gnash";
http://launchpadlibrarian.net/49257319/Derror.txt
--
Bzr 2.1.1 broken through HTTP proxy
https://bugs.launchpad.net/bugs/
So, there are two quite different things happening here. 2.2b3 and
newer include a fix for the lp: urls to work through https_proxy
(though usually that would be https_proxy=http://host:post/ - we
haven't tested with an https listening proxy.
Nevertheless, that part is fixed and has a separate bug
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/49203571/Dependencies.txt
--
Bzr 2.1.1 broken through HTTP proxy
https://bugs.launchpad.net/bugs/586341
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-
20 matches
Mail list logo
