[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: Hyrum K. Wright <hyrum_wright_at_mail.utexas.edu>
Date: Thu, 5 Mar 2009 12:34:23 -0600

On Mar 5, 2009, at 12:03 PM, 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.

This is a feature, not a bug. :)

We actually saw this on our own repository several months ago, and
have since fixed the log messages to be compliant. I suspect we'll
see this type of complaint a lot on user@ once 1.6 is released. I
don't recall what the official stance is on this, but we'd probably
ought to mention it on the Release Notes.

-Hyrum

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1273190
Received on 2009-03-05 19:34:39 CET

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