subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark P." <...@peralex.com>
Subject svn x-shelve gives E200014: Checksum mismatch
Date Tue, 30 Jul 2019 11:57:39 GMT
Good day,

I'm trying to use svn x-shelve on Windows, both via TortoiseSVN and via
the command line client, and I'm getting the above error.  I'm using
subversion version 1.12.2 everywhere.  I'm accessing the repositories
using svn://

After seeing this error on an existing repository, I:
- created a fresh repository with nothing in it,
- checked out the new repository to a working copy,
- added a single file (main.cpp) with a few random lines of text in it,
- committed the add,
- altered the file,
and then ran (from the command line):

svn x-shelve shelf1

I get the following output:

Updating '.svn\experimental\shelves\v3\7368656c6631-001.wc':
At revision 1.
Sending        main.cpp
Transmitting file data .svn: E200014: Checksum mismatch for
'C:\Shared\Test\Test3\.svn\experimental\shelves\v3\7368656c6631-001.wc\main.cpp':
   expected:  b77dd03a6c3f68f496d874153363694e
     actual:  7f081249d3e4e1383afb2798d46a58f5

TortoiseSVN gives a similar, but less descriptive, error.

This happens reliably, with any file I choose to add, when the
repository and the working copy are on a FreeBSD machine and a Windows
machine respectively.  Other repositories seem to do the same thing.

When I try the same thing, with the same repository, but with the
working copy on the FreeBSD machine (still accessed via svn://), it
works as expected.

When I try the same thing with a similar repository on the Windows
machine (accessed via file://), and the working copy on the same Windows
machine, it also works correctly.

All other functionality seems to work fine (checkouts, commits, diffs,
logs, etc.) with repositories on the same machines.  I've tried doing
svn cleanup on the working copies, but I still have the same problem.

Has anybody seen the same problem?  Is this something I'm doing wrong,
or is it a bug?

Thanks
Mark

Disclaimer: http://www2.peralex.com/disclaimer.html



Mime
View raw message