[
https://issues.apache.org/jira/browse/SVN-4650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15993872#comment-15993872
]
Johan Corveleyn commented on SVN-4650:
--------------------------------------
Hi Steffen,
Yes this is definitely an annoying issue. It shouldn't be too hard to fix
(since svnrdump and svnsync can do it), but unfortunately we have a shortage of
hands to do work like this. In case you would have the time to take a stab at
this yourself, a patch to the dev list would be most welcome (but no worries if
you don't ... we're all struggling to get things done).
In the meantime, I can point you to this mailinglist-post from some months ago,
where I explained how we did our dump+load, including how to "fix" your
repository to avoid this issue:
https://svn.haxx.se/users/archive-2016-06/0098.shtml
Another alternative is to use the --bypass-prop-validation flag of 'svnadmin
load', but that would preserve the "invalid property values" in your new
repository.
> svnadmin load of format 4 repositories - no way to normalize line endings if
> CR snuck in an svn:* prop in an earlier release.
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: SVN-4650
> URL: https://issues.apache.org/jira/browse/SVN-4650
> Project: Subversion
> Issue Type: Improvement
> Components: svnadmin
> Affects Versions: 1.8.16, 1.9.4
> Reporter: Eric Johnson
> Priority: Minor
>
> If a repository has svn:* properties (rev-props or normal props) with a CR in
> them, then it is possible to do an svnadmin dump, followed by a load, but
> only with a --bypass-prop-validation. However, that just punts the problem
> down the road to a future release. It is possible to fix all the revprops
> with existing tools, but regular svn:* props cannot be fixed by available
> tools. Only manually editing the dump file will fix the svnadmin load problem
> in this case.
> At least with 1.8 and later (that I've tested), svnsync will normalize line
> endings. So svnadmin load, and svnsync are inconsistent on this topic.
> As near as I can tell, Subversion removes the CRs on output for clients, and
> the no-longer acceptable CR is only visible to svnlook and svnadmin commands.
> In addition, it looks like it removes them on input in current releases. I
> think this means that Subversion clients will not be able to detect the CRs
> in a property. I believe this means that removing the CRs should just work in
> all cases.
> Filed this issue as per this email:
> https://mail-archives.apache.org/mod_mbox/subversion-users/201608.mbox/%[email protected]%3E
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
