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

Re: non-existent revision after dump + svndumpfilter

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: 2004-02-20 08:15:22 CET

"Gerald Richter" <richter@ecos.de> writes:

> Hi,
> we have a large svn repository we need to split into mutiple, so I run a
> svnadmin dump and svmdumpfilter to split out the needed subtree and loaded
> it into a new svn repository. This works fine and I get exact the desired
> result.
> My problem is there are a lot of exiting working copis and I want to be able
> to switch them without haveing to do a new checkout (because actually
> nothing changed and if all users do a new checkout this would cause a lot of
> network traffic over a slow link). So I tried svn switch --relocate which
> works, but doing a svn up afterwards gives me a "Reference to non-existent
> revision XXX' in the Apache error log.
> Of course this revision does not exist, because of the svndumpfilter, the
> new respository has fewer revision then the old one.

Did you run svndumpfilter with the --drop-empty-revs option? If you
want to preserve those working copies, *don't do that*. If you drop
empty revisions, there's no way you'll get all those working copies
synchronized again.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Feb 20 08:16:21 2004

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.