On Fri, Sep 30, 2011 at 5:53 PM, Konstantin Kolinko
<knst.kolinko_at_gmail.com>wrote:
> 2011/10/1 PR <rp0013_at_gmail.com>
> >
> > 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?
>
source : 1.4.6 as5 64 bit server
target : 1.7. rc3 as5 64 bit server
svnsync is the 1.7 rc3
to access source : http protocol to write to dest \ target repo : file:///
>
> >
> > 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
>
> The more known URL to the same book is
> http://svnbook.red-bean.com/index.en.html
>
>
> http://svnbook.red-bean.com/nightly/en/svn.reposadmin.maint.html#svn.reposadmin.maint.replication
>
>
my search returned that result hence .. but yes agree those are the well
known urls ...
> >
> > 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.
>
yes right for now the special user is the only one who can write there
(just a back ground .. we have this wrapper around the sudo command to be
a root user without really knowing the password .. my guess is some race
condition perhaps causing a revision to be skipped ...from the source and
the higher rev on the source gets in as the skipped version on the target
...)
if it helps in one of the repos that this happened i did not see any diff ..
so the file was just added with null text in it .. so a diff -c on that rev
showed no diff at all... i will look more closely ...
>
> Best regards,
> Konstantin Kolinko
>
Received on 2011-10-01 07:47:04 CEST