Reputation: 33
we have a svn repository on a server, and some clients updating/commiting to it.
Now, the server crashed yesterday and the backup available is a week ok old, and has an older svn head saved. Let's say the Head from the backup is revision 2895.
The clients however have revision ie. 2930. When I try to commit to the server, I get an error that the revision on the server is a older one. I can't check in, I can't upgrade and I can't commit.
Has anybody an idea of what I can do to either increment the revision's counter on the server, or how to make a commit under this circumstances?
Thanks in advance.
Upvotes: 3
Views: 2425
Reputation: 234644
You can make a non-versioned temporary copy of the working copy at rev2930, check out rev2895 to a new folder, overwrite with the copy you made and commit to rev2896. This will require everyone else to do something similar (if they don't have any changes in their working copy, they can just check out a new working copy from rev2896).
Upvotes: 0
Reputation: 2155
One solution is to make a checkout in a new folder and replace the files with the modified ones, then try to commit.
I'm not an expert and there may be a more elegant solution though.
Upvotes: 0
Reputation: 5978
Can't you copy locally your 2930, revert to 2895 and then commit everything back to 2896?
Upvotes: 1