Re: 1.6 svn: prop eol-style strictness: breaking svnsync and subclipse

On Mon, Apr 6, 2009 at 11:56, Daniel Shahaf <d.s_at_daniel.shahaf.name> wrote:
[...snip...]
> 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

Only the most recent [1] svnsync patch is really a candidate. My
earlier attempts did not handle svn:log.

[1]: http://svn.haxx.se/dev/archive-2009-04/0023.shtml

> Is there anything left to be done here, or do these workarounds close the
> issue for you?

Yes, I can manage with the identified workarounds and patches, however:

I don't like relying on an out-of-tree patch on svnsync (even if I
wrote it myself). IMO, it would be better if Subversion itself
incorporated a fix to address this issue. I still see this as a
symptom of a design/implementation oversight in 1.6. This should be
addressed, and not left to fester.

[off-topic for this list] I was gald to see that this is begin
addressed on the Subclipse trunk. We may need to back port this fix
for developers stuck on older RAD versions. I'm willing to just
wait-and-seed on this.

// Ben

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1560889
Received on 2009-04-06 13:43:41 CEST