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

Subversion migration using svnsync from 1.4.6 to 1.7

From: PR <rp0013_at_gmail.com>
Date: Fri, 30 Sep 2011 17:00:39 -0700

Hello,

I had initially got a lot of great feedback from the group.

I had decided to migrate the repo using the svnsync and the new server is
1.7 rc3 for the POC migration. (old server 1.4.6).

Initially every thing was smooth now we are noticing that some repositories

we get a failure in sync and that fails with following error

svnsync: E000022: Commit created rev 3912 but should have created 3913

and what i notice is that the 3912 on the source is actually missed and the
3913 comes in as 3912 ..on the target repo ..
the other thing is that this rev is saved as root .. (since i am running as
sudo, the post rev prop has not got a chance to change it to the actual
owner ) ..

any help or pointers?

I did search the error and tried to use the suggestion made some places with
use of

http://code.google.com/p/svnbook/source/browse/trunk/en/book/ch05-repository-admin.xml

svnsync: E000022: Destination repository already contains revision history;
co
nsider using --allow-non-empty if the repository's revisions are known to
mirr
or their respective revisions in the source repository
$ svnsync initialize --allow-non-empty file:///path/to/mirror-repos \
file:///path/to/repos
Copied properties for revision 32042.
$

but that does not seem to help either.

any help will be much appreciated ...

the other way is the long and laborious dump and load from old to new
server... but that too is not without its share of frustration .in terms of
dump then tar and then load.

Regards,
Rajesh
Received on 2011-10-01 09:07:54 CEST

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.