You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Jordan <jo...@formativegroup.com> on 2006/05/01 19:45:02 UTC
apparent file locks when using WebDAV
Hello all,
I recently set-up our SVN/Trac dev environment. It's all working great.with
one exception; I can't seem to write (put) to the svn repositories via
WebDAV (SVN extension in Dreamweaver). I can read the repositories, and can
check things out from them, but I can't put the edited files back into the
repository or add new files. First thing I thought to check were the dir
permissions, but I checked all the perms on all the repo dirs, and
everything is set correctly. Apache is set to use the default "system user"
credentials, and that user has 777 rights to all the repo dirs.
Here is the associated entry from our Apache error log:
[Mon May 01 12:20:25 2006] [error] [client 69.237.248.233] Attempted to lock
non-existent path; turn on autoversioning first. [405, #405]
Here is the associated entry from our Apache access log:
69.237.248.233 - *username* [01/May/2006:12:34:37 -0700] "PUT
/svn/photoalliance/robots.txt HTTP/1.1" 409 614
Anyone else seen this behavior before?
cheers,
Jordan Hilsenbeck
Web Technologist
F O R M A T I V E
801 Folger Avenue
Berkeley, CA 94710
Direct: 510 859-0200 ext. 113
Cell: 415 286-7774
<http://www.formativegroup.com> www.formativegroup.com
Re: apparent file locks when using WebDAV
Posted by Erik Huelsmann <eh...@gmail.com>.
[ .... ]
> I can't seem to write (put) to the svn repositories via
> WebDAV (SVN extension in Dreamweaver). I can read the repositories, and can
> check things out from them, but I can't put the edited files back into the
> repository or add new files.
[ .... ]
> Here is the associated entry from our Apache error log:
> [Mon May 01 12:20:25 2006] [error] [client 69.237.248.233] Attempted to lock
> non-existent path; turn on autoversioning first. [405, #405]
Well, did you? (turn on autoversioning) The log item tells you what to do...
> Here is the associated entry from our Apache access log:
>
> 69.237.248.233 - *username* [01/May/2006:12:34:37 -0700] "PUT
> /svn/photoalliance/robots.txt HTTP/1.1" 409 614
> Anyone else seen this behavior before?
Yes, everybody who has set up their repositories for use with general
DAV clients. How to set up your repository correctly in such cases is
documented in The Book (http://svnbook.org/).
bye,
Erik.
Re: apparent file locks when using WebDAV
Posted by Erik Huelsmann <eh...@gmail.com>.
This is a users@ question. Just because you were not answered quick
enough there doesn't make it a dev@ question.
On 5/2/06, Jordan <jo...@formativegroup.com> wrote:
>
>
> ________________________________
>
>
> From: Jordan [mailto:jordan@formativegroup.com]
> Sent: Monday, May 01, 2006 12:45 PM
> To: jordan@formativegroup.com
> Subject: apparent file locks when using WebDAV
>
>
>
>
> Hello all,
>
>
>
> I recently set-up our SVN/Trac dev environment. It's all working great…with
> one exception; I can't seem to write (put) to the svn repositories via
> WebDAV (SVN extension in Dreamweaver). I can read the repositories, and can
> check things out from them, but I can't put the edited files back into the
> repository or add new files. First thing I thought to check were the dir
> permissions, but I checked all the perms on all the repo dirs, and
> everything is set correctly. Apache is set to use the default "system user"
> credentials, and that user has 777 rights to all the repo dirs.
>
>
>
>
> [Jordan]
>
> Does anyone know if this is being caused because my SVN instance is set to
> use lock-modify-unlock? How can I change this so that incremental adds can
> be committed by separate remote users without checking a doc out first?
> Would this be switching from lock-modify-unlock to copy-modify-merge? Where
> are the instructions on how to change that?
>
>
>
>
>
>
> Here is the associated entry from our Apache error log:
>
> [Mon May 01 12:20:25 2006] [error] [client 69.237.248.233] Attempted to lock
> non-existent path; turn on autoversioning first. [405, #405]
>
>
>
> Here is the associated entry from our Apache access log:
>
> 69.237.248.233 - *username* [01/May/2006:12:34:37 -0700] "PUT
> /svn/photoalliance/robots.txt HTTP/1.1" 409 614
>
>
>
> Anyone else seen this behavior before?
>
>
>
>
>
> cheers,
>
>
>
> Jordan
>
>
>
>
>
>
>
>
>
> --
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.1.385 / Virus Database: 268.5.1/328 - Release Date: 5/1/2006
>
Re: apparent file locks when using WebDAV
Posted by Ryan Schmidt <su...@ryandesign.com>.
On May 2, 2006, at 02:30, Jordan wrote:
> Does anyone know if this is being caused because my SVN instance is
> set to use lock-modify-unlock? How can I change this so that
> incremental adds can be committed by separate remote users without
> checking a doc out first? Would this be switching from lock-modify-
> unlock to copy-modify-merge? Where are the instructions on how to
> change that?
I... don't understand. Subversion is copy-modify-merge. If you want
to enforce a lock-modify-unlock model, the way to do so is to enforce
the use of the svn:needs-lock property. The way to do that is to 1)
distribute a config file to your users which sets the svn:needs-lock
property on all files, and 2) install a pre-commit hook rejecting
commits which do not obey that policy. If you did these two things,
then it should be obvious how to undo it to get back to allowing copy-
modify-merge...
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
RE: apparent file locks when using WebDAV
Posted by Jordan <jo...@formativegroup.com>.
_____
From: Jordan [mailto:jordan@formativegroup.com]
Sent: Monday, May 01, 2006 12:45 PM
To: jordan@formativegroup.com
Subject: apparent file locks when using WebDAV
Hello all,
I recently set-up our SVN/Trac dev environment. It's all working great.with
one exception; I can't seem to write (put) to the svn repositories via
WebDAV (SVN extension in Dreamweaver). I can read the repositories, and can
check things out from them, but I can't put the edited files back into the
repository or add new files. First thing I thought to check were the dir
permissions, but I checked all the perms on all the repo dirs, and
everything is set correctly. Apache is set to use the default "system user"
credentials, and that user has 777 rights to all the repo dirs.
[Jordan]
Does anyone know if this is being caused because my SVN instance is set to
use lock-modify-unlock? How can I change this so that incremental adds can
be committed by separate remote users without checking a doc out first?
Would this be switching from lock-modify-unlock to copy-modify-merge? Where
are the instructions on how to change that?
Here is the associated entry from our Apache error log:
[Mon May 01 12:20:25 2006] [error] [client 69.237.248.233] Attempted to lock
non-existent path; turn on autoversioning first. [405, #405]
Here is the associated entry from our Apache access log:
69.237.248.233 - *username* [01/May/2006:12:34:37 -0700] "PUT
/svn/photoalliance/robots.txt HTTP/1.1" 409 614
Anyone else seen this behavior before?
cheers,
Jordan
--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.385 / Virus Database: 268.5.1/328 - Release Date: 5/1/2006