B Smith-Mannschott wrote on Sat, 4 Apr 2009 at 22:21 +0200:
> On Tue, Mar 31, 2009 at 10:11, B Smith-Mannschott <bsmith.occs_at_gmail.com> wrote:
>
> > The other option, I see is to have svn 1.6 remain as it is, while
> > teaching svnadmin load to understand
> > --normalize-svn-property-eol-style so that old commits don't kill
> > svnsync. (alternately teach this to svndumpfilter).
>
> I dusted off my "Subversion Revisionist" from the great repository
> migration of 2007 and discovered that I had already implemented
> eol-style normalization for properties there. (Apparently Subclipse on
> Windows had been giving us mixed eol-style trouble even back then.)
>
> revisionist-fixprops.py -p "svn:*" -n < old.dump > new.dump
>
> This does the trick if you're using at least 1.0.1 (which added
> globbing in property names).
>
Excellent. So, for now there are 4 workarounds:
* use revisionist-fixprops.py to fix the repository
* use a pre-1.6 destination server to skip the checks
* use 'svnadmin load' at the destination (rather than svnsync) to skip the checks
* apply one of your svnsync patches to fix the repository as it's copied
Is there anything left to be done here, or do these workarounds close the
issue for you?
Thanks,
Daniel
> It's here, if anyone's interested: http://github.com/bpsm/svn-revisionist/
>
> // Ben
>
> ------------------------------------------------------
> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1545694
>
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1560318
Received on 2009-04-06 11:57:29 CEST