2010/3/3 Kutter, Martin <martin.kutter_at_siemens.com>:
I am forwarding the original post below, in case someone else will
encounter similar problem. In my case the issue is, that I have no
idea which files are broken. While doing sync or checkout I just get
the following error in logs:
[Wed Mar 03 11:07:53 2010] [error] [client 192.168.16.18] Provider
encountered an error while streaming a REPORT response. [500, #0]
[Wed Mar 03 11:07:53 2010] [error] [client 192.168.16.18] A failure
occurred while driving the update report editor [500, #185005]
[Wed Mar 03 11:07:53 2010] [error] [client 192.168.16.18]
Decompression of svndiff data failed [500, #185005]
I have no idea how to find out which files are broken. While doing
checkout I get the message like:
svn: REPORT z '/svn/!svn/vcc/default': Decompression of svndiff data failed
Turns out that I can actually check out whole svn/dir1/dir2/dir3/dir4
and even svn/dir1/dir2/dir3/, with no error whatsoever.
Original post included:
> The steps:
> 1. set up path-based authorization using svnserve or
> Apache httpd. See the SVN Book on how to do this.
> 2. Deny access to the broken files to anyone in the
> auth config. This looks like this:
> * =
> 3. Set up a mirror of the repository using svnsync.
> See again the SVN Book on how to do this - typically
> it involves running
> svnsync init destination source
> svnsync sync destination
> Svnsync will ignore files it does not have access to,
> so you get a mirror of your repo without the broken files.
> 4. Create a dump of the synced repository using
> svnadmin dump
> Now you can move your old repository to a save place,
> re-create it and load the created dump into it.
Received on 2010-03-03 11:18:31 CET