Ian Bevan wrote:
> I have found a way to reproduce this problem;
>
> 1. On machine A, create a new file and commit it.
> 2. On machine B, create a file with the same name in the same folder.
> 3. On machine B, perform an update on the folder with the file in it.
> 4. Get a "This file already exists" error.
> 5. From now on, all updates give the "File not found: transaction...."
> message.
>
> Clean up does not work. The only solution appears to be to rename or delete
> the folder.
>
> Note that I found this accidentally. It turns out that Microsoft Visual
> Studio will create an empty .cpp for a file referred to in a .vcproj project
> that does not exist. This in turns causes subversion to freak out, as
> described above.
>
> Note also that this is NOT the only cause of this error, it's just one that
> I found I can reproduce.
>
> Platforms: All winxp pro, running svnserve.
Aha! This is a valuable recipe, thanks!
It seems that *everyone* reporting this bug is using win32, so I'm
betting this almost certainly has to do with the working copy choking on
case-insensitivity issues. It gets confused about case, and then asks
the repository about a file using incorrect case, and the repository
replies with "file not found".
Can you file this as a bug, Ian? It would be great to sic some svn
developers on this recipe to narrow down the exact cause.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri May 7 07:36:51 2004