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*
I found the problem!!!notdefinedMarch 21 2008, 20:52:25 UTC
I've been using the instructions in the documentation section 7.2 titled Installing the Files. This is the example of the SVN Install: # mkdir /home/lj # chown lj:lj /home/lj $ cd $LJHOME $ mkdir cvs $ cd cvs $ svn co http://code.sixapart.com/svn/vcv/trunk vcv $ svn co http://code.sixapart.com/svn/livejournal/trunk livejournal $ cd $LJHOME $ cvs/vcv/bin/vcv --conf=cvs/livejournal/cvs/multicvs.conf --checkout -s
These instructions fail as I indicated before. If i issue the svn commands via sudo like this:
If the checkout fails halfway through, then you can just issue an "svn up" to update the half-checked out tree to current. I've gotten this error a few times myself and just issue subsequent "svn up"s to bring my tree to a consistent state.
Comments 9
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
# mkdir /home/lj
# chown lj:lj /home/lj
$ cd $LJHOME
$ mkdir cvs
$ cd cvs
$ svn co http://code.sixapart.com/svn/vcv/trunk vcv
$ svn co http://code.sixapart.com/svn/livejournal/trunk livejournal
$ cd $LJHOME
$ cvs/vcv/bin/vcv --conf=cvs/livejournal/cvs/multicvs.conf --checkout -s
These instructions fail as I indicated before. If i issue the svn commands via sudo like this:
sudo svn co http://code.sixapart.com/svn/livejournal/trunk livejournal
everything works just fine.
Thanks for all of your help.
Tom
Reply
Reply
Reply
Leave a comment