What I did instead was a propedit on r24 and r25 of the newly loaded
repository to replace the svn:log message. But sync still fails in the
I successfully used this method once before on a similar problem on a
different repository - but the error message in that case referred to
the svn:log as the cause of the problem.
When I do proplist on the new master repo I do not see an ignore
property. Is there a way to find the ignore property? - or are you
sure the actual offending EOL is somewhere else?
The 1.4 version repository is not really mine to tweak. Would this work
on my newly loaded repo on 1.6 ?
From: John Waycott [mailto:javajohn_at_cox.net]
Sent: Friday, June 05, 2009 6:27 AM
To: Andersen, Krista
Cc: users_at_subversion.tigris.org; users-subscribe_at_subversion.tigris.org
Subject: Re: dump 1.4 -> load 1.6 sync fail svn:ignore
On Jun 4, 2009, at 4:52 PM, Andersen, Krista wrote:
I have a Subversion 1.4 repository on a Linux machine. I have created a
dumpfile and loaded it to a repository on our main server (Sparc Solaris
10, Subversion 1.6). This was successful.
This new repository has a hook script to sync to another
write-through-proxy mirror (also on Sparc Solaris 10, Subversion 1.6)
The sync fails on rev 24 every time I attempt to sync.
Transmitting file data
Committed revision 24.
Copied properties for revision 24.
svnsync: At least one property change failed; repository is unchanged
svnsync: Error setting property 'ignore':
Could not execute PROPPATCH.
[Wed Jun 03 10:34:20 2009] [error] [client 10.0.100.127] Could not
execute PROPPATCH. [500, #206]
[Wed Jun 03 10:34:20 2009] [error] [client 10.0.100.127] Cannot accept
non-LF line endings in 'svn:ignore' property [500, #125005]
NOTE: I did a test migration of this repository a few months ago that
did not cause any sync errors. We were using Subversion 1.5 at that
How to I track down the svn:ignore property that is causing this error
in the (successfully loaded) master repository so that I can edit out
the offending EOL?
The problem is most likely the EOL bug in svn:log entries. SVN 1.6 does
not accept carraige returns in svn:log entries.
Here's a python script that you can run against the original 1.4
repository to fix it. Once that is done you will be able to sync. The
bug is fixed in 1.6.3, but that is not available yet, so I had to write
this so we could move forward with our upgrade.
-- John Waycott
This message is for the named person's use only. This communication is for
informational purposes only and has been obtained from sources believed to
be reliable, but it is not necessarily complete and its accuracy cannot be
guaranteed. It is not intended as an offer or solicitation for the purchase
or sale of any financial instrument or as an official confirmation of any
transaction. Moreover, this material should not be construed to contain any
recommendation regarding, or opinion concerning, any security. It may
contain confidential, proprietary or legally privileged information. No
confidentiality or privilege is waived or lost by any mistransmission. If
you receive this message in error, please immediately delete it and all
copies of it from your system, destroy any hard copies of it and notify the
sender. You must not, directly or indirectly, use, disclose, distribute,
print, or copy any part of this message if you are not the intended
recipient. Any views expressed in this message are those of the individual
sender, except where the message states otherwise and the sender is
authorized to state them to be the views of any such entity.
Securities products and services provided to Canadian investors are offered
by ITG Canada Corp. (member CIPF and IDA), an affiliate of Investment
Technology Group, Inc.
ITG Inc. and/or its affiliates reserves the right to monitor and archive
all electronic communications through its network.
ITG Inc. Member FINRA, SIPC
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-06-05 20:48:58 CEST