On Mon, Oct 23, 2006 at 04:14:23PM -0700, Christopher Gardner wrote:
> Our repository uses the svn protocol for access. The repository has an admin group and a users group. The users group has rw access from the trunk directory down. For certain files these user need to use locks. They can successfully acquire locks, make changes, and commit those changes (automatically releasing the locks). When they apply the no-unlock option to svn commit, however, they receive the following messages:
> svn: Commit failed (details follow):
> svn: Authorization failed
> Members of the admin group have no problems using the no-unlock option. I'm guessing there's some option in the authz file I need to set. What am I doing wrong?
That's a good question. It would probably help if you were able to
create a reduced test case (starting from a blank repository), or at the
very least posted your authz file.
The --no-unlock switch to commit doesn't really do very much, it just
skips the unlock step that normally happens after committing with lock
tokens held. You didn't say whether or not users can run 'svn unlock'
Received on Fri Oct 27 03:23:20 2006
- application/pgp-signature attachment: stored