Patrick Markiewicz wrote:
> Hi,
>
> I’m running into an issue. Occasionally, subversion fails
> during a checkout with an error such as “Can’t move
> ‘working\path\to\.svn\tmp\entries’ to ‘working\path\to\.svn\entries’:
> Access is denied.” E.g.:
>
> Normally using an update will fix the problem. However, I’ve been
> consistently running into the following. When I try to execute an
> update on the “working\path\to”, I receive the following error message
> “Working copy ‘working\path\to’ locked. Please execute the “cleanup”
> command. E.g.:
>
>
>
> NOTE: In between these 2 steps, I discovered a suggestion to exclude the
> working directory from a virus scanner, so that the paths in the
> screenshots don’t line up. I basically restarted with a working
> directory of ‘C:\Projrect\DDN Source’
>
>
>
> When I execute the cleanup command, it says:
>
> Can’t open directory ‘working\path\to’. Access is denied. E.g.:
>
>
>
> Why is the directory locked? Why is access denied to the cleanup
> command? How should I proceed? Thanks.
Usually, if even the cleanup fails your only option is to remove the
whole directory and check it out again.
As for the access-denied errors, yes they usually happen because of
virus scanners opening (and locking) every file any application even
touches. Make *sure* you've exluded your working copy paths (some virus
scanners let you exclude paths, but I found some of them still 'check'
files in the exlcuded paths because the application accessing them is
*not* excluded).
There are other programs that might access your files there (desktop
search engines for example).
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
Received on 2008-03-07 22:12:28 CET