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

Re: svnadmin dump - Help Appreciated

From: John Szakmeister <john_at_szakmeister.net>
Date: 2005-11-30 11:48:40 CET

On Tuesday 29 November 2005 09:37, Bryan D. Andrews wrote:
> Anyone have any thoughts on this? We went ahead and did exports,
> checkouts and copied over... it is a huge ordeal as you can imagine with
> different development groups.
> It would be a great thing if the corking copies did not have to get
> "blown away" to get back in action.

Unfortunately, no, there is no other way. It's definitely an ordeal, but
that's to be expected since you lost data. The revision number is expected
to be monotonically increasing. Restoring from a backup breaks that because
rX-rY (the revisions that were lost) will represent something different in
the new repository. :-( Plus, base revisions the working copy expects to
exist, don't any more. This breaks the delta-based transfer that occurs
between the client and server.

All of that said, there is discussion of a checkout feature that would allow
you to check out on top of an existing source tree but you wouldn't have to
download source files that already exist in the source tree (if they match).
That might be useful in this case, because you could blow away the .svn
directories and overtake the source tree with a new checkout that would have
all the correct information. Your new working copy would probably show a lot
more changes, and you might have to re-add or delete some files (depending on
the changes you had made), but it might be useful for these situations.
Unfortunately, I don't know what the status of that feature right now.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Nov 30 12:04:23 2005

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.