Summary: | bzr.eclass complains with "ERROR: Invalid url supplied to transport" if a proxy is supplied | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Eric Thibodeau <kyron> |
Component: | Eclasses | Assignee: | bazaar+obsolete |
Status: | RESOLVED UPSTREAM | ||
Severity: | normal | CC: | ulm, xmw |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://bugs.launchpad.net/bzr/+bug/330823 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Eric Thibodeau
2010-09-13 14:03:23 UTC
Ok, does youe http_proxy string work on the command line with e.g. w3m/wget/links/... or bzr itself? (In reply to comment #1) > Ok, does youe http_proxy string work on the command line with e.g. > w3m/wget/links/... or bzr itself? Sorry, I didn't see that reply come through, the answer is yes. The proxy setting is valid and I have been using it with most of the other tools/means of emerging packages (and it's also used for browsers and manually with wget). So I know there isn't a typo in the proxy setting. I checked the manpage (iirc) and there was no mention on handling proxies. As https://bugs.launchpad.net/bzr/+bug/330823 mentions: use http://<proxy-server>:80/ which is the way bzr interprets those variables. So I'd say this is UPSTREAM. |