You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Michael Clark <mc...@comcast.net> on 2006/06/06 10:06:40 UTC

Annoying SVN behavior ": run 'svn cleanup' to remove locks (type 'svn help cleanup' for details)"

 

All starts out working fine, I'm chugging along and every thing is happy.
Then I get the working copy locked message, no problem just run cleanup. But
that doesn't work. What I end up having to do is to manually delete the
folder. This generally happens several time when checking out the entire
source tree.

Any Ideas ?

 

H:\bf\trunk>svn up

svn: Working copy '.' locked

svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for details)

 

H:\bf\trunk>svn cleanup

svn: Can't move 'Enterprise/apache2/modules/aaa/.svn/tmp/entries' to
'Enterprise/apache2/modules/aaa/.svn/entries': Permission denied

 


RE: Annoying SVN behavior ": run 'svn cleanup' to remove locks (type 'svn help cleanup' for details)"

Posted by Michael Clark <mc...@comcast.net>.
That did the trick. Switching from cygwin to native win32 and everything is
happy now. Thanks!

-----Original Message-----
From: D.J. Heap [mailto:djheap@gmail.com] 
Sent: Friday, June 09, 2006 5:37 PM
To: Michael Clark
Cc: users@subversion.tigris.org
Subject: Re: Annoying SVN behavior ": run 'svn cleanup' to remove locks
(type 'svn help cleanup' for details)"

On 6/9/06, Michael Clark <mc...@comcast.net> wrote:
> Sorry about the delayed response
>
>
> Original command
> h:\bf>svn co https://svn.bf.org/svn/Bf/trunk h:\bf\trunk
>
> svn: Can't move 'h:\bf\trunk/Enterprise/BFW/.svn/tmp/entries' to
> 'h:\bf\trunk/Enterprise/BFW/.svn/entries':
> Permission denied
>


Have you tried the native (not cygwin) client to see if it happens?

DJ

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

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

Re: Annoying SVN behavior ": run 'svn cleanup' to remove locks (type 'svn help cleanup' for details)"

Posted by "D.J. Heap" <dj...@gmail.com>.
On 6/9/06, Michael Clark <mc...@comcast.net> wrote:
> Sorry about the delayed response
>
>
> Original command
> h:\bf>svn co https://svn.bf.org/svn/Bf/trunk h:\bf\trunk
>
> svn: Can't move 'h:\bf\trunk/Enterprise/BFW/.svn/tmp/entries' to
> 'h:\bf\trunk/Enterprise/BFW/.svn/entries':
> Permission denied
>


Have you tried the native (not cygwin) client to see if it happens?

DJ

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

RE: Annoying SVN behavior ": run 'svn cleanup' to remove locks (type 'svn help cleanup' for details)"

Posted by Michael Clark <mc...@comcast.net>.
Sorry about the delayed response


Original command 
h:\bf>svn co https://svn.bf.org/svn/Bf/trunk h:\bf\trunk

svn: Can't move 'h:\bf\trunk/Enterprise/BFW/.svn/tmp/entries' to
'h:\bf\trunk/Enterprise/BFW/.svn/entries':
Permission denied


-----Original Message-----
From: D.J. Heap [mailto:djheap@gmail.com] 
Sent: Tuesday, June 06, 2006 7:43 AM
To: Michael Clark
Cc: users@subversion.tigris.org
Subject: Re: Annoying SVN behavior ": run 'svn cleanup' to remove locks
(type 'svn help cleanup' for details)"

On 6/6/06, Michael Clark <mc...@comcast.net> wrote:
> All starts out working fine, I'm chugging along and every thing is happy.
> Then I get the working copy locked message, no problem just run cleanup.
But
> that doesn't work. What I end up having to do is to manually delete the
> folder. This generally happens several time when checking out the entire
> source tree.
>
> Any Ideas ?


What was the original failure that locked the working copy?


>
>
>
> H:\bf\trunk>svn up
>
> svn: Working copy '.' locked
>
> svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for
details)
>
>
>
> H:\bf\trunk>svn cleanup
>
> svn: Can't move
> 'Enterprise/apache2/modules/aaa/.svn/tmp/entries' to
> 'Enterprise/apache2/modules/aaa/.svn/entries': Permission
> denied


Sounds like you are using the cygwin client.  Try using the native
client and see what happens.  The cygwin client doesn't include some
workaround code for Window's tag-alongs like virus scanners, indexers,
etc.  Another possibility is that you are using a network drive of
some sort for your working copy and something is wrong with it --
hardware failures, network failures, etc.

DJ

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

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

Re: Annoying SVN behavior ": run 'svn cleanup' to remove locks (type 'svn help cleanup' for details)"

Posted by "D.J. Heap" <dj...@gmail.com>.
On 6/6/06, Michael Clark <mc...@comcast.net> wrote:
> All starts out working fine, I'm chugging along and every thing is happy.
> Then I get the working copy locked message, no problem just run cleanup. But
> that doesn't work. What I end up having to do is to manually delete the
> folder. This generally happens several time when checking out the entire
> source tree.
>
> Any Ideas ?


What was the original failure that locked the working copy?


>
>
>
> H:\bf\trunk>svn up
>
> svn: Working copy '.' locked
>
> svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for details)
>
>
>
> H:\bf\trunk>svn cleanup
>
> svn: Can't move
> 'Enterprise/apache2/modules/aaa/.svn/tmp/entries' to
> 'Enterprise/apache2/modules/aaa/.svn/entries': Permission
> denied


Sounds like you are using the cygwin client.  Try using the native
client and see what happens.  The cygwin client doesn't include some
workaround code for Window's tag-alongs like virus scanners, indexers,
etc.  Another possibility is that you are using a network drive of
some sort for your working copy and something is wrong with it --
hardware failures, network failures, etc.

DJ

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