[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: bug that leads to corrupt revision

From: Ryan Schmidt <subversion-2007b_at_ryandesign.com>
Date: 2007-10-26 22:26:31 CEST

On Oct 26, 2007, at 14:23, Boris Unterer wrote:

> I accidentally added two files in the same folder whose filename
> only differ in case:
>
> Splash.jpg
> Splash.JPG
>
> Now that revision (573) is corrupted. checkout (svn co -r 573
> <url>) fails with
>
> svn: REPORT Anfrage fehlgeschlagen auf ?\194?\187/svn/CPC/!svn/vcc/
> default?\194?\171
> svn: REPORT von ?\194?\187/svn/CPC/!svn/vcc/default?\194?\171: 200
> OK (<url>)
>
> And verify fails with
> * Revision 572 verifiziert.
> svnadmin: Pr?\195?\188fsummenfehler beim Lesen der Darstellung:
> Erwartet: cdfbec37d27da67257b1e570b6d19304
> Tatsächlich: 3eb8afefc114e25e2d057531a3e9713e
>
> I tried to dump/load the repository, with omission of the broken
> revision 573, but was not successful: verify then fails on revision 0.
>
> How can I fix that?

This is a curious variation on the usual only-differs-in-case error
describe in the FAQ. I'm not sure how to fix it now. Hopefully
someone else will. But I think a pre-commit hook might have prevented
it (if you installed a pre-commit hook that prevents commits of files
whose names differ only in case).

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Oct 26 22:29:24 2007

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.