Re: Bug report

2009/4/29 KlasNordberg <klas.nordberg_at_gmail.com>:
> Sorry for the confusion,
>
> Yes, I appears that BOTH (1) and (2) are needed to cause this
> problem.  Only (1) causes a "standard" update failure since the
> already open file cannot be replaced, but it recovers after a cleanup
> and a new update.  But (2) is needed to make things go really bad.
>
> Yes, I mean "working copy" where it says "local repository".
>
> No, I don't think that I can reproduce the error on the command line.
> I run Windows and there is no command line version of SVN on my
> machine as far as I can see, only TSVN.

No, it is a separate download. You can get it from

http://www.collab.net/downloads/subversion/

Get the Windows client installer (3MB). Unfortunately you have to
register, but it is a free download.

> We have also linux machines
> here with command line SVN, but since it is possible to update a file
> in the file system system even if it is open in unix, it should not
> cause the same problem.

Almost certainly this is a problem within the subversion libraries,
but the only way to be sure is to download the official command line
client and try it. That will also allow you create a script/batch file
that reproduces the problem, which is useful because the subversion
developers will not use TortoiseSVN to do their debugging.

Simon

-- 
:       ___
:  oo  // \\      "De Chelonian Mobile"
: (_,\/ \_/ \     TortoiseSVN
:   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
:   /_/   \_\     http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=1979905
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].