Hi all,
I have been using subversion on a Debian Sarge server where I commit from both TextMate on Mac and Emacs on Linux workstation. Everyting worked great and I was upto revision 13 (this sounds spooky around halloween :) and yesterday when I firedup Textmate it upgraded to 1.5.4(1311). I commtied at the end of the day to rev 13 with no errors. However when I tried svn update on my Linux ws I got
svn: REPORT request failed on '/svn/zstaff/!svn/vcc/default' svn: The REPORT request returned invalid XML in the response: XML parse error at line 126: Extra content at the end of the document . (/svn/zstaff/!svn/vcc/default)
I am using web-dav with Apache2 on the server with digest auth. Now my repo is borked I cannot do anything with it. Posted to the subversion list and haven't gotten any answers.
First of all does this have something to do with the TextMate update? That is the ONLY thing that changed.
I am no subversin expert and would appreciate any help in troubleshooting and fixing this problem. Is there any way to recover the repo? Googling for it hasn't helped. I think the first line of the msg can happen to a variety of conditions. But I couldn't find anything on how to fix the problem due to XML parse error in . /svn/zstaff/!svn/vcc/default
thank you very much,
bakki
On 2. Nov 2006, at 17:06, Bakki Kudva wrote:
svn: REPORT request failed on '/svn/zstaff/!svn/vcc/default' svn: The REPORT request returned invalid XML in the response: XML parse error at line 126: Extra content at the end of the document . (/svn/zstaff/!svn/vcc/default)
This sounds very much like an svn error, and caused by something wrong on the server.
I am using web-dav with Apache2 on the server with digest auth [...]
Do you know if the repository is backed by BerkleyDB or fsfs? The former, I am told, is prone to corruption (and everyone today uses the latter).
First of all does this have something to do with the TextMate update? That is the ONLY thing that changed.
Unlikely -- TM runs the ‘svn’ shell command, and that one can’t do things which can’t be reversed (and are generally harmless).
On 11/2/06, Allan Odgaard throw-away-1@macromates.com wrote:
This sounds very much like an svn error, and caused by something wrong on the server.
You might be right. I am using the old darwin ports subversion1.3.1_0. Wonder if there are any issues with this.
I am using web-dav with Apache2 on the server with digest auth [...]
Do you know if the repository is backed by BerkleyDB or fsfs? The former, I am told, is prone to corruption (and everyone today uses the latter).
I did not specify --fs-type fsfs to svnadmin create. I am using subversion 1.1 on the server which supposedly uses BerkeleyDB by default. I have been reading a bit on how to "rewind" the DB in the Book. Don't yet know if this will solve the problem.
First of all does this have something to do with the TextMate update? That is the ONLY thing that changed.
Unlikely -- TM runs the 'svn' shell command, and that one can't do things which can't be reversed (and are generally harmless).
thanks for the reply. I would appreciate any other pointers from svn gurus on the list :)
-bakkik
-
Allan Odgaard -
Bakki Kudva