> I've posted the following bug report to dev@ mailing list about a
> As it got no response I'm going to repeat it here.
> The bug must have been introduced somewhere between 1.5.3 and 1.5.5,
> noticed it after the upgrade of both client and server sides from
> For a repository, some users are granted full rw access from the root
> downwards, while other users
> may access only specific subtrees in it. The access.conf looks like
> @full = user1,user2
> @full = rw
Have you tried adding to here:
otheruser = r
> otheruser = rw
> Now this restricted user can check-out his working copy of
> /some/path/beneath without problem.
> He can also make queries with `svn status -u' or `svn info http://URL'
> But an attempt to make an
> update of the working copy leads to the following mysterious message:
> svn: Server sent unexpected return value (403 Forbidden) in response
> OPTIONS request for 'http://our.server/svn/Repo'
> In the server log the following record appears:
> Access denied: 'otheruser' OPTIONS Repo:/
> Provider encountered an error while streaming a REPORT response.
> A failure occurred while driving the update report editor [500,
> It gives the impression that `svn update' tries to access something at
> root of the repository,
> which it formerly (<=1.5.2) did not need. (We have no external
> this repository).
> If it is not a bug but a new feature, it effectively renders our
> permission scheme absolutely useless.
If it's a root-level issue, maybe the suggestion above about giving
read-only access at the root level will work for you.
As to why access above that level is needed, I don't know. Maybe
something related to mergeinfo?
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-02-24 23:46:13 CET