subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Shahaf <...@daniel.shahaf.name>
Subject Re: Subversion migration using svnsync from 1.4.6 to 1.7
Date Sat, 01 Oct 2011 06:06:33 GMT
Konstantin Kolinko wrote on Sat, Oct 01, 2011 at 04:53:01 +0400:
> 2011/10/1 PR <rp0013@gmail.com>
> > 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?

Yes.  An error code has a default message associated with it, but when
an error object it constructed the callsite can specify an alternative
message.

> I'd think that the error code in the book is wrong. Though there it is
> actually for the "initialize" command.

I'm surprised that it's an errno error code rather than a Subversion
error code from svn_error_codes.h.  (I can tell that by its numeric
value.)

> 

If the book is wrong, please report it to the book's mailing list.  If
you think Subversion should promise a specific error code in this
situation, please file a bug against svnsync.

Mime
View raw message