Error connecting to svn.apache.org
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. I've tried over hotspot (T-Mobile USA), and wifi with the same reults (I was wondering if it was an IPv4 / IPv6 issues). However if I do: $ svn log https://github.com/apache/synapse.git ... it works as expected. Github's Svn mirrors don't require the /trunk suffix for 'master' that's mapped to that. Does anyone have any ideas? - Paul
Re: Error connecting to svn.apache.org
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 context: The server unexpectedly > closed the connection. > > I've tried over hotspot (T-Mobile USA), and wifi with the same reults > (I was wondering if it was an IPv4 / IPv6 issues). > > However if I do: > > $ svn log https://github.com/apache/synapse.git > > ... it works as expected. Github's Svn mirrors don't require the > /trunk suffix for 'master' that's mapped to that. > > Does anyone have any ideas? Nope ... All I can say is that it works for me. FWIW: $ host svn.apache.org svn.apache.org has address 209.188.14.144 Could be different for you. -- Brane
Re: Error connecting to svn.apache.org
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/trunk' svn: E175009: The XML response contains invalid XML svn: E130003: Malformed XML: no element found at line 1 ^ That as an attempt to force IPv4
Re: Error connecting to svn.apache.org
Hmmm, OK this shifts the problem: mv ~/.subversion ~/.subversionOLD I mean doing the log operation after that now works as expected. - Paul
Re: Error connecting to svn.apache.org
Dammit, false alarm - there was a proxy definition in there just for svn.apache.org :-( :-(
Re: Error connecting to 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).
Re: Error connecting to svn.apache.org
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 at URL > 'https://dist.apache.org/repos/asf/synapse/trunk' > svn: E175009: The XML response contains invalid XML > svn: E130003: Malformed XML: no element found at line 1 > > ^ That as an attempt to force IPv4 This does not so much force IPv4 as it breaks name-based virtual hosts on the server ... which is obvious from the bogus redirect. -- Brane
Re: Error connecting to svn.apache.org
> 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.
Wildcard bug? Or user error?
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 wildcards several times today, so I just tried in a clean freshly checked-out copy: E:\workspace\processor>svn rm *.hconfig svn: E25: Use --force to override this restriction (local modifications may be lost) svn: E25: 'E:\workspace\processor\a' is not under version control There is no file or directory named 'a' here; however many files in this directory have names that begin with the letter 'a'. Furthermore, when working in the command line earlier today, it appeared that the names printed in the error messages were truncated versions of filenames. In this case the filename was truncated to just one character but I think I saw more characters in other filenames earlier (not 100% sure on this point). Other (possibly useful) information: There are no files whose names differ only in case. The filenames do not contain spaces (nor do any of the paths, whether in the repo or my working copy). There are no properties set on this directory or any of its files. Also, I tried similar operations on freshly checked out copies of other areas of the repo and the same phenomenon is manifesting. I don't recall ever seeing this before. Thoughts?
