Martin Knauf wrote:
> Am 26.09.2006, 00:07 Uhr, schrieb Garrett Rooney
> <rooneg@electricjellyfish.net>:
>
>> On 9/25/06, Erik Huelsmann <ehuels@gmail.com> wrote:
>>
>>> On 9/25/06, Martin Knauf <martinmk@gmx.de> wrote:
>>> > Hi,
>>> >
>>> > we have an annoying bug with file which are locked by Windows.
>>> Mostly this
>>> > files are dll file which are used by a programm.
>>> >
>>> > Wenn this files are used and you update you svn folders you'll get an
>>> > error message that the file couldn't be overwriten. The Result of
>>> this
>>> > action is, that you can download the whole svn again. There is no
>>> way to
>>> > work further with this folder.
>>> >
>>> > Could you please fix it!
>>>
>>> No, this is a windows problem. There's no way to overwrite files in
>>> use by other programs: to that extent, there's no way to update your
>>> working copy...
>>
>>
>> Well, he seems to be implying that running an update in that situation
>> results in a busted working copy. That seems bad. I'd love to see
>> some actual transcripts of this problem...
>>
>> -garrett
>
>
>
> ok, here is Tortois log windows message wenn the file is in use:
>
> Updated: C:\test\test2.dll
> Updated: C:\test\test.dll
> Error: In directory ' C:\test'
> Error: Can't move ' C:\test\test.dll.tmp' to ' C:\test\test.dll':
> Zugriff verweigert
>
> after closing the program which is using the file und doing an update
> again:
>
> Error: Working copy 'C:\test' locked
> Error: Please execute the "Cleanup" command.
>
> cleaning up:
>
> Subversion reported an error while doing a cleanup!
> ---------------------------------------------------
> In directory 'c:\test'
> Can't copy 'c:\test\.svn\tmp\text-base\test2.dll.svn-base' to
> 'c:\test\test2.dll.2.tmp': Das System kann die angagebene Datei nicht
> finden.
>
> System can't find given file.
>
> test2.dll is a file that was updated at the same time as test.dll but
> not locked by a program.
>
I used to get this behaviour fairly often. My solution was to delete the
whole folder with the offending file in it, then do an svn update. No
need to delete the whole working copy ...
Of course, the fact that (parts of) the working copy can get broken this
way does suggest there may be a bug.
In my case, it seemed to be the virus scanner which caused the locked
files. Now I've set the virus scanner to ignore my working copies, and
everything's OK.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Sep 26 11:33:40 2006