views:

47

answers:

4

We had a series of unfortunate events with our VisualSVN server yesterday and we are trying to get back on track today. I have recreated the repository as suggested in this stackoverflow post.

We recreated the repository with a co-workers working copy folder (svn-export, svn-import). But now when he tries to update we get an error message about the UUID's not matching. Can I update his working copy to get the UUID's to match or are we going to have to now delete his working copy and recreate that as well?

A: 

would svn relocate do the trick?

If everything was imported into the repository and you wouldn't lose anything, I'd play it safe and just re check it out (in a new directory).

Alan Jackson
A: 

I'm not sure there's a way to fix and match the UUID's up.

But: what's so tricky about recreating his working copy? A simple checkout will suffice.

Wim Hollebrandse
+1  A: 
Michael Hackner
A: 

Everyone will have to check out their working copies again. We have experienced this before.

For those that were negligent in frequently checking in they should check out a new working directory in parallel, do a directory diff with the old working copy, review the changes, and copy from the old working directory to the new working directory any changes that they are comfortable with.

Dan