> Per your Issue Tracker Guidelines, I am seeking somebody who agrees > that this is a bug before I submit it. > > Overview: For files, 'svn mv' does not properly inherit ACL > permissions from the parent directory. > > Steps to reproduce (from a subversion working directory): > 1. setfacl -d -m user:$USER:r-x . > 2. touch foobar > 3. svn add foobar > 4. svn commit -m 'test' foobar > 5. svn mv foobar barfoo > 6. getfacl barfoo > > If you check the ACL for barfoo after steps 2, 3, and 4, you will see > that it has properly inherited the user:jdoe:r-x permission. After > step 5, you will see that barfoo has not. You can circumvent this > behavior by using "mv" instead of "svn mv" in step 5. In this case, > you need to "svn delete foobar" and "svn add barfoo" before you can > commit the move. > > Details: > CentOS release 5.4 (Final), svn 1.4.2 (from yum) > > I'm not sure what else is relevant, so fire away if you have questions.
svn 1.4 is MILES old. I'm not a core dev here but I expect that you should attempt this issue with the current 1.6.11 before reporting it as a bug. BOb
