[Ns-bugs] [Bug 307] pybindgen not fetchable via web proxy

[bugzilla-daemon@nsnam-www.ece.gatech.edu]

http://www.nsnam.org/bugzilla/show_bug.cgi?id=307


gjcarneiro at gmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |gjcarneiro at gmail.com




------- Comment #1 from gjcarneiro at gmail.com  2008-09-04 07:06 -------
(In reply to comment #0)
> I've not been able to retrieve pybindgen from behind a proxy, despite setting
> https_proxy and Ubuntu Preferences->Network Proxy.  Is there some other way to
> configure proxy support for bzr?
> 
> This is a typical error:
> Trying to fetch pybindgen; this will fail if no network connection is
> available.
>  =>  /usr/bin/bzr checkout -rrevno:572 https://launchpad.net/pybindgen
> /home/user/hg/ns-3-dev/bindings/python/pybindgen
> bzr: ERROR: Invalid url supplied to transport: "Host empty in:
> proxy.example.com"
> 
> I'm not sure whether this is a bzr problem (have Googled and found some people
> asking about bzr's proxy support)

Try upgrading bzr, or setting the http_proxy environment variable.  Luckily in
the release tarballs bzr will not be used, so this is a problem for ns-3
developers only.

> but I think that, regardless, if this occurs,
> a more prominent error should display at the end of ./waf configure that alerts
> the user to the lack of Python support.

So you are saying that lack of Python support is more important than e.g. lack
of Gtk support, so that it deserves an additional warning in the end?  Or do
you think we should perhaps present a summary in the end of all optional
features, saying if they are enabled or not?  If seen such summaries in some
configure scripts in some projects before...


-- 
Configure bugmail: http://www.nsnam.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.