Ben Collins-Sussman wrote:
> On Sun, 2004-03-14 at 22:31, Folker Schamel wrote:
>
>>svn: REPORT request failed on '/svn/repository/!svn/vcc/default'
>>svn: The REPORT request returned invalid XML in the response: XML parse error at
>> line 1: no element found (/svn/repository/!svn/vcc/default)
>
>
> This is a mod_dav_svn bug that was fixed in 1.0.1.
Ahh, nice to know! Thanks! :-)
>>When performing a merge for a particular subdirectory,
>>I always get the following error immediately:
>>
>>svn: REPORT request failed on '/svn/repository/!svn/vcc/default'
>>svn: REPORT of '/svn/repository/!svn/vcc/default': Could not read response body: co
>>nnection was closed by server. (http://192.168.0.1)
>
>
> This looks like a server-side crash; are you sure your errorlog doesn't
> say anything about that?
The apache2 error log says:
[Mon Mar 15 05:34:17 2004] [error] [client 192.168.0.2] Provider encountered an error while streaming a REPORT response. [500, #0]
[Mon Mar 15 05:34:17 2004] [error] [client 192.168.0.2] A failure occurred while driving the update report editor [500, #160005]
[Mon Mar 15 05:34:17 2004] [error] [client 192.168.0.2] Invalid editor anchoring; at l
>>A recovery does not help.
>
>
> Why would you need to recover? Did the repository get stuck?
Not knowing details about the implementation,
I wanted to exclude that a wired repository state
is responsible for the problems.
>>The problem is, that I cannot update (important) changes
>>from the trunk into a branch, and I don't know a work-around.
>
>
> You'll need to show us an exact transcript of what you're doing.
I know that this would be the best...
The problem is that it is a larger repository, about 1 GB.
The actual action simply was an classical merge
command to merge changes from trunk into a branch.
Maybe the above apache2 log message about the "update report editor"
failing with "500" and "#160005" and the "invalid anchoring"
alrady helps at least a little bit?
Cheers,
Folker
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Mar 16 00:07:18 2004