For svn 1.10.2, when I do:
$ svn log http://svn.apache.org/repos/asf/synapse/trunk
it results in:
svn: E170013: Unable to connect to a repository at URL '
http://svn.apache.org/repos/asf/synapse/trunk'
svn: E120108: Error running context: The server unexpectedly closed the
connection
On 02.09.2018 21:04, Paul Hammant wrote:
> For svn 1.10.2, when I do:
>
> $ svn log http://svn.apache.org/repos/asf/synapse/trunk
>
> it results in:
>
> svn: E170013: Unable to connect to a repository at URL
> 'http://svn.apache.org/repos/asf/synapse/trunk'
> svn: E120108: Error running
I'd already tried something similar, but will paste in the result:
$ svn log http://209.188.14.144/repos/asf/synapse/trunk/
Redirecting to URL 'https://dist.apache.org/repos/asf/synapse/trunk':
svn: E170013: Unable to connect to a repository at URL
'https://dist.apache.org/repos/asf/synapse/
Hmmm, OK this shifts the problem:
mv ~/.subversion ~/.subversionOLD
I mean doing the log operation after that now works as expected.
- Paul
Dammit, false alarm - there was a proxy definition in there just for
svn.apache.org :-( :-(
I'm not sure if there's a online definitive error guide for Svn, but
if there is the page for E170013 could be enhanced to suggest "check
your darn proxy settings in ~/.subversion/servers, fool" (or less
Paul-centric language).
On 02.09.2018 21:22, Paul Hammant wrote:
> I'd already tried something similar, but will paste in the result:
>
> $ svn log http://209.188.14.144/repos/asf/synapse/trunk/
> Redirecting to URL 'https://dist.apache.org/repos/asf/synapse/trunk':
> svn: E170013: Unable to connect to a repository
> This does not so much force IPv4 as it breaks name-based virtual hosts
> on the server ... which is obvious from the bogus redirect.
Yup, I guessed as much too. I just pasted it in because I'd seen it
offered as advice online somewhere.
Has there been a recent change to how wildcards (the asterisk '*') is
treated under Windows?
I am using command line client 1.10.2 r1835932 as installed with
TortoiseSVN 1.10.1, Build 28295 - 64 Bit , 2018/07/15 12:14:12, on
Windows 10 Home 1803 build 17134.254.
I've encountered weirdness with wi
