[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: I believe I have found a bug with 'svn mv' + ACL-protected files.

From: Mark Slade <markandrewslade_at_gmail.com>
Date: Thu, 29 Apr 2010 10:00:35 -0400

Bob,

Thanks for the tip. My mistake.

Mark

On Thu, Apr 29, 2010 at 9:50 AM, Bob Archer <Bob.Archer_at_amsi.com> wrote:

> > 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
>
Received on 2010-04-29 16:01:03 CEST

This is an archived mail posted to the Subversion Dev mailing list.