[
https://issues.apache.org/jira/browse/SVN-4414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14932588#comment-14932588
]
Ivan Zhakov edited comment on SVN-4414 at 10/18/15 11:58 AM:
-------------------------------------------------------------
'svnrdump' (dump and load) is also affected.
Issue SVN-4476 covers fixing 'svnrdump' for the r0 case. The general case
should be addressed here.
was (Author: julianfoad):
{noformat:nopanel=true}
'svnrdump' (dump and load) is also affected.
Issue #4476 covers fixing 'svnrdump' for the r0 case. The general case should be
addressed here.
{noformat}
> dump/load with invalid mergeinfo
> --------------------------------
>
> Key: SVN-4414
> URL: https://issues.apache.org/jira/browse/SVN-4414
> Project: Subversion
> Issue Type: Bug
> Components: libsvn_repos
> Affects Versions: all
> Reporter: Philip Martin
> Fix For: nonblocking
>
> Attachments: 1_x.x
>
>
> Partial dump parses mergeinfo, in order to issue warnings if the mergeinfo
> refers to revisions outside the partial dump, and if the parse fails the dump
> fails. This is less than ideal since it stops users fixing the mergeinfo by
> editing the dumpfile. Dump should issue a warning, rather than stop with an
> error, should produce a dumpfile containing the invalid mergeinfo.
> Load also parses the mergeinfo, in order to renumber, and so it won't load a
> dumpfile with invalid mergeinfo. That means users must fix the mergeinfo
> before loading. I suppose we could allow load when renumbering is not
> necessary, i.e. a full dumpfile into an empty repository.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
