You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@subversion.apache.org by "Daniel Shahaf (äñ§€¥£¢ JIRA)" <ji...@apache.org> on 2017/11/01 15:25:00 UTC

[jira] [Commented] (SVN-4623) no-op prop change not preserved across dump/load

    [ https://issues.apache.org/jira/browse/SVN-4623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16234207#comment-16234207 ] 

Daniel Shahaf (äñ§€¥£¢) commented on SVN-4623:
----------------------------------------------

https://svn.apache.org/r1813898 fixes this for FSFS.

> no-op prop change not preserved across dump/load
> ------------------------------------------------
>
>                 Key: SVN-4623
>                 URL: https://issues.apache.org/jira/browse/SVN-4623
>             Project: Subversion
>          Issue Type: Bug
>    Affects Versions: all
>            Reporter: Philip Martin
>            Priority: Minor
>
> svnadmin create repo
> svnmucc -mm -U file://`pwd`/repo mkdir A propset p v A
> svnmucc -mm -U file://`pwd`/repo propset p v A
> The log of r2 shows status 'M' for the path '/A', this is true for FSFS, BDB and FSX.
> svnadmin create repo2
> svnadmin dump repo | svnadmin load repo2
> The log of r2 after a dump/load does not show '/A' as status 'M'.
> Note that if the first repo has 'enable-rep-sharing=false' then the 'M' status does get preserved by the dump/load.
> See svnadmin_tests.py:dump_no_op_prop_change.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)