Tortoise SVN having hernias over existing local copies.
From: Warren Kinny <wjkinny_at_resmaster.com>
Date: 2005-10-20 18:06:15 CEST
We have been using Tortoise SVN for about 9 months.
We have a development team in Australia, and one in UK.
Both sites have local copies of the source code (in identically
However, we keep upsetting Tortoise in the following way :
1) Someone emails a new source record direct to the other party,
2) The sending party subsequently does a SVN Commit.
3) Later again, the receiving party attempts to do a SVN Update
Subsequent attempts to re-update the receiving end produce such memorable
"File not found: transaction '7y', path '/BP/WS/<some existing file name>'
(where the file name in question is NOT one that was changed locally or
Tortoise Cleanups do NOT solve the problem, and essentially the only thing
I HAVE SOME BASIC QUESTIONS THEREFORE :
1) If Tortoise can happily merge changes into existing files, and identify potential
2) Is there anything that can be done to fix the pickle without having to delete
3) Are we missing the basic boat here ? Is tortoise designed to cope with the
Is it as simple as always running updates and commits in a certain order ?
Any simple knowledgeable pointers greatly appreciated !!
--Received on Thu Oct 20 17:12:19 2005
This is an archived mail posted to the TortoiseSVN Users mailing list.