2010/2/25 curtis osterhoudt <flutz...@yahoo.com>
> I would like to mention that the server which hosts the LyX svn
> development trunk is configured in such a way that some places may have
> problems pulling in the code. For example, from home, I have no problems
> downloading LyX using svn. From work (a very security-conscious place), the
> same commands will fail, giving virtually no clues as to why, and yet svn
> checkouts and updates work from *other servers* when used from my workplace.
> What I have to do there is ssh into yet another computer on the "outside",
> svn update from there, and then snag the results to my work computer.
> Despite the hassle, 2.0 has been worth it.
>
> I have no idea why this happens, despite several concerted days of trying
> different things, emailing both the LyX server maintainer and our security
> people, etc., who all had good suggestions but no definitive answers. My
> best guess at this point is that our work firewall/proxy system was somehow
> hung up on particular configuration flags from the svn server.
>
> So, fellow LyXers, if your svn commands fail somehow (some recent
> messages have indicated that they might), it might just not be your fault!
>
>
>
>
Well known issue - svn protocol itself does not support (and probably will
not) proxying of any kind. This causes problems in offices where your PC is
behind proxied firewall (as in my case). Only solution to that is to host
svn+http or svn+https or svn+ssh (if your SSH may work through your proxy;
in my case not currently). Generally it is not non-standard to host svn
protocol alone as the LyX project do.
--
Manveru
jabber: manv...@manveru.pl
gg: 1624001
http://www.manveru.pl
