The only thing from your log that caught my attention is !svn (shouldn't it be .svn?). So the question is -- which operating system/SVN version are you using?
That was a reply from the sixapart server. The only thing I sent was the svn co line. I've tried this on OSX Leopard and Linux with the same result.
A livejournal/htdocs/doc/server/ljp.dbschema.usertrans_churn.html A livejournal/htdocs/doc/server/ljp.csp.flat.getchallenge.html svn: REPORT request failed on '/svn/livejournal/!svn/vcc/default' svn: The REPORT request returned invalid XML in the response: XML parse error at line 36288: no element found (/svn/livejournal/!svn/vcc/default)
I'm sorry, but I'm not reproducing this. I just used the very same command you've provided and checked it out successfully.
Though quick google turns out that this can be triggered by non-ASCII commit messages. I'm using Unicode (UTF-8) at my Gentoo box, so maybe changing the encoding at your own Linux system can help. *shrug*
Reply
A livejournal/htdocs/doc/server/ljp.dbschema.usertrans_churn.html
A livejournal/htdocs/doc/server/ljp.csp.flat.getchallenge.html
svn: REPORT request failed on '/svn/livejournal/!svn/vcc/default'
svn: The REPORT request returned invalid XML in the response: XML parse error at line 36288: no element found (/svn/livejournal/!svn/vcc/default)
Reply
Though quick google turns out that this can be triggered by non-ASCII commit messages. I'm using Unicode (UTF-8) at my Gentoo box, so maybe changing the encoding at your own Linux system can help. *shrug*
Reply
Reply
Reply
Leave a comment