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

checksum fun take 2:

From: <rooneg_at_electricjellyfish.net>
Date: 2003-01-29 00:31:12 CET

ok, this is just my week for checksum errors...

i just got this trying to update my working copy:

[rooneg@CommandLine:~/Hacking/svn ] svn up
svn: Working copy text base is corrupt
svn: could not save file
svn: apply_textdelta: checksum mismatch for
'.svn/text-base/win-tests.py.svn-base':
    expected checksum: f9c9027cfe19f92f7f6e1b9d3d316acf
    actual checksum: 9f30bad101c64a873b0f2c05d529924c

[rooneg@CommandLine:~/Hacking/svn ] vi
.svn/text-base/win-tests.py.svn-base
[rooneg@CommandLine:~/Hacking/svn ] vi .svn/entries
[rooneg@CommandLine:~/Hacking/svn ] md5 win-tests.py
MD5 (win-tests.py) = 9f30bad101c64a873b0f2c05d529924c
[rooneg@CommandLine:~/Hacking/svn ] md5
.svn/text-base/win-tests.py.svn-base
MD5 (.svn/text-base/win-tests.py.svn-base) =
9f30bad101c64a873b0f2c05d529924c
[rooneg@CommandLine:~/Hacking/svn ]

as far as i can tell, the 'expected' checksum is just wrong compared to
what i've got, both in the text base and in my working copy's main
directory. unfortunately, it's not easy to see what's in the actual
entries file, since it's an old-style checksum... how can i see if
this actually matches what i've got?

entry
    committed-rev=4371
    name=win-tests.py
    text-time=2002-12-12T23:32:10.000000Z
    committed-date=2003-01-13T22:43:13.497183Z
    checksum=+ckCfP4Z+S9/bhudPTFqzw==
    last-author=rassilon
    kind=file
    prop-time=2003-01-13T23:40:01.000000Z/

is anyone else seeing this kind of error?

-garrett

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 14 02:23:05 2006

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

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