Blocker Description
We are running an subversion 1.4.3 server through apache 2.2.3 on an XServe G5/10.4.8/8L127 apr/apr-util version 1.2.8 The svn client in use is 1.4.2. The repository's size is approx. 59000 revisions. Revision 58158 cannot be checked out because there is a corrupted file(?) in that revision. Upon checkout, update, verify, diff, merge, dump and sync through http://, file://, an error is issued: 'svn: Decompression of svndiff data failed' The server log reveals this: Mon Feb 26 18:01:22 2007] [error] [client xx.xx.23.125] A failure occurred while driving the update report editor [500, #185005] [Mon Feb 26 18:01:22 2007] [error] [client xx.xx.23.125] Decompression of svndiff data failed [500, #185005] We have worked around the problem by identifying the file in question and removing it with a server- side delete and re-adding it from a previous revision. Some questions remain though: How do I get rid of that specific revision such that I can use dumps and svnsync again? Is there a way to repair the repository? Should subversion's error log be chronological? [26/Feb/2007:17:59:21 +0100] commit r58157 [26/Feb/2007:17:59:43 +0100] update '/trunk' [26/Feb/2007:17:59:52 +0100] commit r58159 [26/Feb/2007:18:00:30 +0100] checkout-or-export '/trunk' [26/Feb/2007:18:04:14 +0100] update '/trunk' [26/Feb/2007:17:59:24 +0100] commit r58158 [26/Feb/2007:18:05:04 +0100] commit r58160
Original issue reported by cunger