subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Konstantin Kolinko <>
Subject Re: Subversion migration using svnsync from 1.4.6 to 1.7
Date Sat, 01 Oct 2011 00:53:01 GMT
2011/10/1 PR <>
> 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?

When using svnsync there are usually three versions of svn running:
source server, target server, and the svnsync program itself.  What
version of svnsync you were using? Was it 1.7 rc3 as well? (BTW, rc4
was published recently).

What protocols your svnsync is using to access the source and the
target servers? (file, svn, http(s))?

Your OS - some Unix? Is it 32 or 64 bit?

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

The more known URL to the same book is

> 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.

Can the same error code produce different text messages? I'd think
that the error code in the book is wrong. Though there it is actually
for the "initialize" command.

> 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.

In your target repository - do you check user name in the pre-commit
hook? Only the one special user that svnsync runs as has to be allowed
to write there.

Best regards,
Konstantin Kolinko

View raw message