You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Christopher Dunn <Ch...@Freescale.com> on 2004/09/01 19:39:52 UTC

Problem committing with multiple users on fsfs.

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
  <title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
We want to convert to svn from cvs, but we cannot use the client-server
model. We are using the filesystem model.<br>
<br>
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:<br>
<br>
<span style="font-family: monospace;">bash% svn commit -m "" hello.c</span><br
 style="font-family: monospace;">
<span style="font-family: monospace;">Sending&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; hello.c</span><br
 style="font-family: monospace;">
<span style="font-family: monospace;">Transmitting file data .svn:
Commit failed (details follow):</span><br
 style="font-family: monospace;">
<span style="font-family: monospace;">svn: Can't move
'/proj/svn/db/current.3.tmp' to '/proj/svn/db/current': Operation not
permitted</span><br>
<br>
<br>
We have tried adding read/write permission everywhere in <span
 style="font-family: monospace;">/proj/svn</span>. The umask is not the
problem.<br>
<br>
Here is how the repo was created:<br>
<br>
<span style="font-family: monospace;">svnadmin create --fs-type fsfs
/proj/svn</span><br style="font-family: monospace;">
<br>
Can anyone help us? <br>
</body>
</html>


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

Re: Problem committing with multiple users on fsfs.

Posted by Max Bowsher <ma...@ukf.net>.
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

Re: Problem committing with multiple users on fsfs.

Posted by Greg Hudson <gh...@MIT.EDU>.
> svn: Can't move '/proj/svn/db/current.3.tmp' to '/proj/svn/db/current': Operation not permitted

As Max notes, this is most likely due to an APR bug which causes new
directories to be created with the sticky bit set.  However, it's
easier to work around the bug than he suggested; just "chmod -R o-t"
the repository after it's created, and you should be fine.

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