I did some tests with scm-manager and subversion and it seems to have a strange behaviour when you use path write protection and branch merging. Suppose you have a initial dir context like {tags,trunk,branches} and normal users just have write access inside these directories not in repository's root path using path write protection. Later you create some files and dirs in trunk and after it you copy this into a branch folder down to branches. You do changes in your trunk and in your branch directory. Later you want to merge things again into trunk. Things work fine at svn merge command and later you want to commit this merge into trunk. If you have path write protection enable, a user which is not repository owner is not able do succeed this commit. I don't understand why this happen because a priori the user is not trying to write at repository's root path. If you disable path write protection or gives this user repository owner privileges, he is able to succeed the svn commit command. My tests were done with 1.38 scm-manager version. Is this a bug or an expected behaviour ?
--
You received this message because you are subscribed to the Google Groups "scmmanager" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scmmanager+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.