2009/4/29 Klas Nordberg <klas_at_isy.liu.se>:
> I run TSVN 1.6.1 on SVN 1.6.1 on Windows Vista and have noticed that
> recently it has become more difficult to update files that are already
> in use by some other program.
>
> The PROBLEM:
>
> When I update my local repository under these 2 conditions:
I think you mean that both these conditions must be present?
When you say "local repository" you mean "working copy". You need to
use the correct terms to avoid causing confusion ;-)
> (1) One file that needs to be updated cannot be replaced by the new file
> since it already open by some other application (e.g., a pdf file that
> is already open in the acrobat reader)
>
> (2) A new file has been added to the remote repository
>
> the local repository ends up in a state that cannot be resolved, and I
> need to delete the entire local repository and check it out again. More
> precisely, the update fails since TSVN cannot replace the already opened
> file, when I close the file and try to update again, I am prompted to do
> a cleanup, but the cleanup fails and the error message says something
> about the new file (which has not yet appeared in the local repository)
> is not under version control. From there it appears to be no other way
> than to remove the local repository and check it out again.
>
> To make this problem appear, do like this:
>
> (1) create a new folder in the remote repository, add a pfd and check it
> out at two local repositories (on two machines or on two different
> locations in the file system)
>
> (2) in one of the local copies, change the content of the pdf (but not
> its name), add a new file, and check these changes into the remote repsotory
>
> (3) in the second local repository, open the pdf in acroread
>
> (4) update the changes into the second local repository and the problem
> described above happens (at least to me...)
>
> The failed update problem has been around as long as I have been using
> TSVN, but the failed cleanup appears to be new, I have never been forced
> to delete a local repository to solve it before.
Can you reproduce the problem using the svn command line client? If
so, you should report this on the subversion users mailing list.
Producing a batch file which reproduces the problem will definitely
help to get noticed there.
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=1977522
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-04-29 11:38:55 CEST