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

Re: Trunk svnsync can't sync some existing repos

From: Neels J. Hofmeyr <neels_at_elego.de>
Date: Fri, 21 Nov 2008 02:58:16 +0100

Augie Fackler wrote:
> I'm not sure if this is a "real" bug or not, but it feels like one. With
> 1.4's svnsync, I can make a local copy of
> http://soc.googlecode.com/svn just fine, but with an svnsync built from
> trunk it gets partway through and then complains about line-ending issues.
> Should I file an issue in the BTS?

Please first just post a detailed description of the bug to this list
(which versions did you use, what commands did you issue, what is the output

I submitted a patch once to properly handle inconsistent line-ending style
where the server receives log messages. Previously, it was silently allowed
to store inconsistent line endings in log messages.

We discussed also complaining about inconsistent line-endings when stuff is
read from a server, but we figured it would be best to let users access the
information even though it is inconsistent.

I figure a sync from one repos to another may produce this situation: The
one server contains inconsistent line endings, of old. The other server now
checks incoming data for consistency and refuses to receive.

So, I guess svnsync should automatically correct inconsistent line-ending
styles (check each svn:log revprop, if found inconsistent, send a consistent
version to the other side, or something like that -- might get complex).

I have no time to work on this now, so if you feel inclined to look around
yourself or have others to do that for you, this list will gladly be of

Alternatively, the source repository could be fixed to not contain any
inconsistent line endings.

First, though, to be sure, post a more detailed description, as above.


Received on 2008-11-21 02:58:51 CET

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.