[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Fw: SVN 1.4.0 (r21228): svn commit with no-unlock fails authorization

From: Christopher Gardner <chris_gardner76_at_yahoo.com>
Date: 2006-10-24 01:14:23 CEST

I hope someone on this list can help. I'm running svnserve on Windows Server 2003.

----- Forwarded Message ----
From: Christopher Gardner <chris_gardner76@yahoo.com>
To: users@subversion.tigris.org
Sent: Monday, October 23, 2006 3:36:23 PM
Subject: SVN 1.4.0 (r21228): svn commit with no-unlock fails authorization

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?

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Oct 24 01:14:40 2006

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.