"Jens Geyer" <j...@vsx.net> writes: > I can confirm that. > Deleting is only possible if the user has write permnissions on the > ENTIRE path. > > / top/subdir/mypath > > In order to delete mypath, the user needs write permission on > > / > /top/subdir > /top/subdir > /top/subdir/mypath > > With an 1.6.x server, write access to /top and above were not necessary. > > I could not find any documentation about this changed behavior. Next, it > is not really what we want. I don't want to give all users write access > on the entire tree up to the rootfolder just to enable them to svn > delete their own files and folders.
I can't reproduce this, or your other authz problem, on my Linux machine: $ cat repo/conf/svnserve.conf [general] auth-access = write anon-access = password-db = passwd authz-db = authz $ cat repo/conf/authz [/A/B] pm = rw [/] * = r $ svn ls -R --username pm svn://localhost/repo A/ A/B/ X/ X/Y/ $ svn cp -mm --username pm svn://localhost/repo/X/Y svn://localhost/repo/A/B/C Committed revision 12. $ svn rm -mm --username pm svn://localhost/repo/A/B/C Committed revision 13. $ svn rm -mm --username pm svn://localhost/repo/A/B svn: E220004: Access denied $ svn cp -mm --username pm svn://localhost/repo/X/Y svn://localhost/repo/A/C svn: E220004: Access denied I wonder if there is an upper/lower case problem somewehere in your authz file? Or perhaps in the Subversion authz code? -- Philip
