[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: How to recover when the client is more up-to-date than the server

From: Jacob Atzen <jacob_at_aub.dk>
Date: 2006-06-14 13:20:19 CEST

On Wed, Jun 14, 2006 at 11:21:13AM +0200, Henrik Holst wrote:
> Hello,
> we had an accident where the repository storage crashed hard before
> the daily backup was run so we are now in a situation where the clients
> are seeing revision 69 and the server/repository is seeing revision 60,
> that is 9 revisions where lost due to the crash and missing backup.
> Now, is there any possibility to force out the missing revisions from
> the client somehow? Even if it would be impoissible to exactly recreate
> the 9 revision steps, is there any ways to force out a diff between the
> current state on the clients as revision 61 to the repository and then
> to force the clients to "downgrade" to revision 61?

I would do something like:

- Backup the current working copy to somewhere safe
- Remove every .svn folder from the working copy (thereby making it
- Checkout a fresh working copy from the repository
- Copy the unversioned copy into the fresh working copy
- Commit the differences, creating r61
- Perform a fresh checkout on the rest of the clients

- Jacob Atzen
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jun 14 13:22:19 2006

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.