You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@subversion.apache.org by "Philip Martin (JIRA)" <ji...@apache.org> on 2018/03/16 12:37:00 UTC
[jira] [Created] (SVN-4728) dump/load mergeinfo-mod difference with
--deltas
Philip Martin created SVN-4728:
----------------------------------
Summary: dump/load mergeinfo-mod difference with --deltas
Key: SVN-4728
URL: https://issues.apache.org/jira/browse/SVN-4728
Project: Subversion
Issue Type: Bug
Components: libsvn_fs_fs
Affects Versions: trunk
Reporter: Philip Martin
When a revision is a property-only change to a node that has svn:mergeinfo then a dump/load of that revision produces different representations in new repository depending on whether --deltas is used when dumping.
The original repository:
svnadmin create repo
svnmucc -mm -U [file://|file:///]`pwd`/repo mkdir A
svnmucc -mm -U [file://|file:///]`pwd`/repo propset svn:mergeinfo /B:1 A
svnmucc -mm -U [file://|file:///]`pwd`/repo propset p2 v2 A
Dump and load without --deltas
svnadmin dump repo | svnadmin load repo2
svnadmin dump --deltas repo | svnadmin load repo3
Note the difference in the r3 revision files:
$ grep -a modify-dir repo[23]/db/revs/0/3
repo2/db/revs/0/3:0-1.0.t2-2 modify-dir false true true /A
repo3/db/revs/0/3:0-1.0.t2-2 modify-dir false true false /A
The field that differs is mergeinfo-mod, introduced in 1.9. The problem doesn't occur in earlier versions.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)