ansaurus

Question

Tortoise Check-in error Checksum mismatch

Answer 1

+1 A:

Looks like one of your SVN files is corrupt. First, check-in everything that can safely be checked in, and make sure to backup everything. Then fix the offending file - usually this involves deleting it from your repository. This should be okay if you're checking in a new version anyway.

bkritzer 2009-07-20 23:09:10

Are you sure you need to delete it from the repository? It looks like just the working copy is corrupt. Also, the file is the BASE copy in .svn, normally you don't want to mess around with this directory.

Si 2009-07-20 23:20:48

I agree. It's better to delete the parent and re-update.

bkritzer 2009-07-20 23:40:43

but how can I check in when it's an atomic commit when you commit at the base?

CoffeeAddict 2009-07-21 13:36:09

what do you mean by delete the parent and re-update?

CoffeeAddict 2009-07-21 14:57:01

Another thought: have you tried saving your working copy and reverting to the previous revision (the one before head), then re-committing your working copy?

bkritzer 2009-07-21 15:33:05

If I revert, won't it replace my current code?

CoffeeAddict 2009-07-21 16:11:23

Yes, but you can back up your working copy before reverting, then replace it after the revert.

bkritzer 2009-07-21 18:56:38

well, good thing I don't have too many updates then to merge back or else that would be a nightmare.

CoffeeAddict 2009-07-21 19:24:36

Answer 2

A:

Unfortunately, I can't help. But if you don't get a solution here, then you might have more luck on the subversion users mailing list where lots of experts and (subversion-) developers are present.

M4N 2009-07-20 23:12:28

Nice, the damn forum shows your name...very public, not liking this.

CoffeeAddict 2009-07-21 16:18:25

Answer 3

+4 A:

Something has gotten out of sync or has become corrupt, and because it's in your .svn BASE directory, unless you are confident is tinkering with this, you're probably better off deleting the parent of the .svn directory and then perform an update. Of course take a backup or see if an export works before doing this so you don't lose any changes.

FWIW, I get this sometimes with our library references where Visual Studio seems to keep a lock on some files (even though it's not compiling) and won't let me update them.

Also, I gather xxxx.svn has had it's name changed for SO, because normally it's just .svn.

Si 2009-07-20 23:21:20

so you're saying delete the parent .svn folder?

CoffeeAddict 2009-07-21 13:37:10

I deleted my parent .svn, but then you lose the update command in your context menu..?

CoffeeAddict 2009-07-21 14:01:23

>Also, I gather xxxx.svn has had it's name changed for SO, because normally it's just .svn.It was a posting issue, I wrapped the error above in code tags which renders the real error as I saw it

CoffeeAddict 2009-07-21 16:45:34

Sorry if I wasn't clear; I assumed the problem wasn't at the root of your working copy, thus your parent directory itself has a .svn directory (which knows about it), which means an svn update would pull down a fresh version of the directory and its contents. If it was at root, then yes, I'm afraid a complete new checkout would be required.

Si 2009-07-22 00:10:31

Answer 4

A:

I agree with solution: delete parent folder and update again ===> problem will fixed. I meet this problem and successful with that solution.

Manh Ha 2010-05-06 03:01:29

ansaurus

tags:

views:

answers:

Tortoise Check-in error Checksum mismatch

related questions