Re: Broken WC errornously attempts to add an existing file during commit

Lübbe Onken <l.onken <at> rac.de> writes:

> the files that are causing trouble are files which are created by the
> compiler. It may be that the compiler generated files are detected as
> 'missing' at some point, because they are deleted and overwritten.

But still TSVN/SVN shouldn't autonomously detect and react on such a change. I
would expect to be able to do just anything with the WC files and then be able
to do a commit/status without any issues comparing/commiting the changes since
the last update.

> TortoiseSVN also tries to fix/prevent upper/lowercase filename changes on
> the client side, which the CL client doesn't. Perhaps its a combination of
> the two.

Hm, ok, when and how? Does it revert obvius renames back to rep name? Or move
to the new name of WC?

> If I understand you correctly, your repository is intact, only the working
> copy is FUBAR? So you should be able to check out and do this again? Without
> a reproduction recipe we probably can't help you much.

Yeps, everything was okay in repository. Only the WC in which some changes were
made had gone bad, and as mentioned we could do a new checkout and commit
without any problems. I can see that the my co-worker experiencing this had
done a server side delete of some of the temp files ~, .obj, .tds with the same
basename, after the WC had been last updated, maybe that could trigger
something.

> Did you rename any files/folders in the path without committing the rename,
> before the WC was corrupted?

As far as I have been told no renaming had been done in the WC prior to these
corruptions.

Mikkel,

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Mon May 22 16:10:18 2006