Thank you for quick answer, here is more precise: to my concern, this
user already checked out the
https://oldserver/svn/myrepo1/trunk/something
then he should be able to perform a relocate to
https://NEWSERVER/svn/MYREPO/trunk/something
but this is not happening with permissions like:
[MYREPO:/]
aaa =
[MYREPO:/trunk/src/something]
aaa = rw
-- B.S.
>
> david.x.grierson@jpmorgan.com wrote:
> It's doing exactly what you're asking it to ...
>
> The first entry states that aaa will get no access to anything below
> MYREPO.
>
> The second entry states that aaa will get access to the objects in MYREPO
> /trunk/src/something.
>
> The second entry has no way of over-riding the first - since you can't
> get access to /trunk or even /trunk/src.
>
> Dg.
> --
> David Grierson
> JPMorgan - IB Architecture - Source Code Management Consultant
> GDP 228-5574 / DDI +44 141 228 5574 / Email david.x.grierson@jpmorgan.com
> Sentinel House 2nd floor, 103 Waterloo Street, Glasgow G2 7BW
>
>
>
>
> Bjørnar Skinnes <bskinnes@broadpark.no> 13/08/2007 15:30
>
> To
> users@subversion.tigris.org
> cc
>
> Subject
> Relocate does not work well with access permissions
>
>
>
>
>
>
> Having access permissions like this example:
> [MYREPO:/]
> aaa =
> [MYREPO:/trunk/src/something]
> aaa = rw
>
> then relocating (the repo was moved to another server) the "something"
> working copy, does return error message like this:
> PROPFIND request failed on "/svn/MYREPO"
> PROPFIND of '/svn/MYREPO': 403 Forbidden (https://myserver)
>
> I had to change the permission file, giving aaa read permissions, to
> get aaa up&running:
> [MYREPO:/]
> aaa = r
>
> Why no access for aaa in first place ? Remark: browsing in firefox
> worked fine on new server.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Aug 13 18:14:39 2007