> >> >>> > 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 ...). > > > > The LF check happens in the repos layer, but 'svnadmin load' uses the FS > > API directly so it doesn't trip that check. svnsync can't do this so > > I think it has a (half-supported?) flag to auto-fix non-LF svn:* > > properties. > > Ah, I thought I remembered that I got them auto-repaired when I did an > svnadmin dump + load (with 1.7.x), but I'm not sure anymore (it was > with a test migration a year ago).
I had to use this recently to ignore the non-LF problems when loading with 1.7: svnadmin load --bypass-prop-validation http://svnbook.red-bean.com/en/1.7/svn.ref.svnadmin.html#svn.ref.svnadmin.sw.bypass_prop_validation Kevin R.
