tags:

views:

64

answers:

4

So, my server administrator rolled back the subversion server from a backup. My working copy is at revision 1534, but the server is now at 1525, which yields some problems:

$ svn up
svn: Revision 1534 not found

Of course, there is always the option to do a clean checkout, but is there an easier way to get my local working copy in sync with the server?

+1  A: 
svn up -r HEAD

or specifying another specific revision should work.

Michael Hackner
Sorry, already tried that, same error mesage
rlovtang
Have you tried with the specific revision number? `svn up -r 1525`?
RedGlyph
Yes, same error
rlovtang
This cannot work as svn up (on server) will always try to diff before pulling the update, however there is no such a revision.
Peter Parker
+2  A: 

You have to check out again.

Your working copy is dead.

Your admins should really try to sync their back up on each commit or storing the commits as dumps via hook script

Peter Parker
The sad thing is that this was actually a planned downtime, an upgrade that didn't succeed. I didn't get a notice, and they kept the server alive for 2 more hours after taking the backup.. :(
rlovtang
maybe your admins should learn some svnbasics.. point them to http://subtrain.tigris.org
Peter Parker
A: 

I can't see any solution other than making a new checkout, and manually merging your uncommitted changes into your new working copy. Basically, your working copy comes from a alternate reality -- one where the server upgrade actually worked -- and I don't think Subversion has any provisions fixing this.

JesperE
A: 

The same thing happened to us a few weeks ago. I renamed my trunk folder, checked out a clean trunk and then manually copied all changed files from the crash date and beyond into my trunk so that I could recommit the changes.

kmacmahon
Yes, that's what I ended up doing also.
rlovtang