Christopher Dunn wrote:
> We want to convert to svn from cvs, but we cannot use the client-server
> model. We are using the filesystem model.
>
> Anybody can check out, diff, etc. When the person who created the
> Subversion
> repo commits, no problem. But when a different user commits, he gets a
> message like this:
>
> bash% svn commit -m "" hello.c
> Sending hello.c
> Transmitting file data .svn: Commit failed (details follow):
> svn: Can't move '/proj/svn/db/current.3.tmp' to '/proj/svn/db/current':
> Operation not permitted
>
>
> We have tried adding read/write permission everywhere in /proj/svn. The
> umask
> is not the problem.
You are using APR from apache 2.0.50?
I suspect you will have the sticky bit set throughout your repository and
working copy dirs.
This is due to a bug in the APR shipped with apache 2.0.50 and svn
1.1.0-rc2.
Either upgrade svn to the head of the 1.1.x branch (contains a workaround
for the bug) or upgrade apr to the head of it's 0.9.x branch (or take the
version from the soon-to-be-released apache 2.0.51) AND REBUILD SVN. Merely
installing updated apr shared libs is not sufficient.
Max.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Sep 2 00:27:09 2004