[
https://issues.apache.org/jira/browse/SVN-4650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15984378#comment-15984378
]
Steffen Mazur commented on SVN-4650:
------------------------------------
Hi,
is there any possibility to fix this problem? I found out that an other issue
is related to this. See https://issues.apache.org/jira/browse/SVN-4263
This issue was marked with a priority "major" but this here is marked as
"minor". But I think these are the same problems.
Could it be that the code fix of SVN-4263 only was made in the tool *svnrdump*?
In my opinion the same code fix should be commited in the *svnadmin load* tool.
I have the same problem, that i can't import a dump file (64GB) because of the
following error. (I used the command "svnadmin load")
svnadmin: E125005: Invalid property value found in dumpstream; consider
repairing the source or using --bypass-prop-validation while loading.
svnadmin: E125005: Cannot accept non-LF line endings in 'svn:log' property
Thank you and best regards
Steffen
> 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)
