Unexplicable relation between directory access control and commits of locked files.

Hi all,

I found a behavior which is unexplicable to me. Maybe someone can point
to me the documentation where this is explained.

The Problem: archiving locked files does not work.
I used the following sequence:

te87 mzampare:~/tmp/APE 1149 > svn lock -m "another test" test2.txt
'test2.txt' locked by user 'mzampare'.
te87 mzampare:~/tmp/APE 1150 > echo "and another one" >> test2.txt
te87 mzampare:~/tmp/APE 1151 > svn status test2.txt
M K test2.txt
te87 mzampare:~/tmp/APE 1152 > svn ci -m "trying archiving with lock"
test2.txt
svn: Commit failed (details follow):
svn: Authorization failed

*BUT*

te87 mzampare:~/tmp/APE 1153 > svn unlock test2.txt
'test2.txt' unlocked.
te87 mzampare:~/tmp/APE 1154 > svn ci -m "trying archiving without lock"
test2.txt
Sending test2.txt
Transmitting file data .
Committed revision 235.

The setup:
svnserv.conf contains the line:
authz-db = authz

and the authz file contains (among other things).

[/]
* = r
@admin = rw

This is because (me being a control freak), I do not want any user to
modify the basic root structure of trunk,branches,tags.

The interesting part is that, if I change the above to:

[/]
* = rw
@admin = rw

everything works as expected.

Does anyone know *WHY* ??

thanks,

Michele

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-09-15 17:33:53 CEST