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

Re: Minor regression in svnsync 1.6rc3 (from 1.5.6)

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: Thu, 05 Mar 2009 13:31:26 -0500

Magnus Torfason wrote:
> I just tried syncing my repository to a fresh 1.6rc3 build and got the
> following message:
>
> ...
> Committed revision 75.
> Copied properties for revision 75.
> Committed revision 76.
> Copied properties for revision 76.
> svnsync: Cannot accept non-LF line endings in 'svn:log' property
>
> Turns out that these very old log entries had something strange going on
> in the line endings in the log messages. The workaround was to go back
> and change them (I did it manually using TortoiseSVN). Trivial really in
> my case.
>
> The only reason I mention this is that I retested this on a 1.5.6 build
> (both are running on Linux 2.6.* kernels, although not on the same
> machine), and that worked without a hitch.
>
> My guess is that a test was added in 1.6 (A Good Thing), but perhaps the
> consequences for svnsync were unforeseen? I could imagine scenarios
> where the required changing of log messages would be nontrivial.

I've survive such a required change. I automated it with a loop around
svnsync that, upon error, would use 'svn pget' and 'svn pset' to fix the
messed-up log message, and then resume the synsync loop.

I wouldn't call this a regression really. It's a bugfix with a loud bit of
motivational messaging for cleanup. :-)

-- 
C. Michael Pilato <cmpilato_at_collab.net>
CollabNet   <>   www.collab.net   <>   Distributed Development On Demand
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1273181

Received on 2009-03-05 19:31:47 CET

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