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

Re: Dealing with binaries and migrating a 36G repository

From: Johan Corveleyn <jcorvel_at_gmail.com>
Date: Sat, 13 Apr 2013 09:41:46 +0200

On Sat, Apr 13, 2013 at 9:38 AM, Johan Corveleyn <jcorvel_at_gmail.com> wrote:
> [ Please don't top-post on this list, i.e. put your reply at the
> bottom or inline, thanks. More below. ]
>
> On Sat, Apr 13, 2013 at 6:08 AM, James Marcus <marcus.james_at_gmail.com> wrote:
>> On Fri, Apr 12, 2013 at 9:27 PM, Ryan Schmidt
>> <subversion-2012c_at_ryandesign.com> wrote:
>>>
>>>
>>> On Apr 12, 2013, at 11:35, James Marcus <marcus.james_at_gmail.com> wrote:
>>>
>>> > I actually started a migration with svnsync so that I didn't have to
>>> > worry about network issues related to transferring a single 36GB file on an
>>> > unreliable network. But I ran into this issue: Cannot accept non-LF line
>>> > endings in 'svn:log' property [500, #125005]
>>> >
>>>
>>> You should fix the svn:log property of that revision so that it does not
>>> contain non-LF line endings.
>>>
>> I did fix it, but there are many, how do you deal with hundreds maybe
>> thousands?
>
> I believe svnadmin dump/load (with 1.7) fixes those automatically. So
> one option is to use that (or to use those to create an intermediate
> repository which you can then transfer with svnsync). Or repair the
> svn:log properties in the source repository with some script.
>
> HTH
> --
> Johan

Ah, and perhaps svnrdump also works. Not sure, you'll have to test it
(or perhaps someone else on this list knows ...).

--
Johan
Received on 2013-04-13 09:42:39 CEST

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

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