On Wed, Jul 17, 2013 at 11:52:12AM +0200, Riccardo Mottola wrote: > Hi, > > I need to check out a (known good) repository through https. It is > not a server configuration probelm (as googling woudl suggest) but i > am pretty sure it is a missing package or a configuration of svn, > neon on my OpenBSD box which I was unable to diagnose. > > svn co --username xxx--password yyyy https://someurl/path/trunk/ > > yields: > svn: E175002: Unable to connect to a repository at URL 'xxxxx' > svn: E175002: The OPTIONS request returned invalid XML in the > response: XML parse error at line 1: no element found (xxx)
This looks like a problem in network communication. The client is expecting an XML response but didn't get one. Is the URL you are using correct? If you are sure the URL is correct, I'd like to know if the repository is public so I can try to reproduce the error. > I suppose this is a missing module or a missing option. Perhaps neon > or serf. On FreeBSD I just had to install them and it worked. > > I am using binary packges, a couple of days old. > I have: > serf-1.2.0, neon-0.29.6p1, subversion-1.7.5p0 > > Any further hints? Is neon configured with ssl support in the packages? You don't need to install serf. It is not used by anything yet and will automatically be pulled in as a dependency once I upgrade the Subversion port to 1.8.1 (which will be released next week). I did not upgrade the port to 1.8.0 because that release has too many issues. What's the output of svn --version on your system? It shouldn't show ra_serf, only ra_neon, in the list of supported RA modules. If your package did pick up serf, then I need to fix the port to prevent that. However, Subversion 1.7 will use neon by default anyway, so you won't get to use serf unless you tweak the client configuration. If the URL problem you're having is related to serf, please use neon.
