Interesting topic and sorry the intromission, but I wonder, after creating that branch with an user who has full recursive permissions, if there is a low administrative effort way of persisting original access rights, since the path changed. This should be accomplished without having to create specific new rules for this new path on the authz file.
Luiz Guilherme -----Mensagem original----- De: Daniel Shahaf [mailto:d...@daniel.shahaf.name] Enviada em: sexta-feira, 30 de julho de 2010 04:35 Para: Neil Gray (Chemstations) Cc: users@subversion.apache.org Assunto: Re: Branching from Working Copy with Partial Visibility Neil Gray (Chemstations) wrote on Thu, Jul 29, 2010 at 14:49:59 -0700: > Hello. > > My subversion repository has some directories with restricted access > configured by the authz file. This works very well, and checkouts with > partial visibility. > > However if I need to make a branch, I cannot seem to do that with partial > visibility. In all cases that I have tried the svn copy is stopped by an > access denied error. > > Is there any way to normally branch and merge from directories that contain > items that I do not have permission to see? > > Neil If you attempt 'svn cp /foo /bar' and you can't see some of /foo's children, I expect the copy to succeed but only copy what you have access to see. Is that not the case? I do not expect it to be possible to make a full recursive copy of a directory that has children you can't see. (that would be a security hole: who guarantees the authz is configured so those children remain unviewable-by-you after the copy?) So, if you want to branch that thing, do so as someone with full recursive read permissions.