[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

bug?: "commit failed, file already exists"

From: Christian Bang <cbang_at_gmx.net>
Date: 2006-05-05 09:51:31 CEST


I get the above error every time the first commit crashes for some
reason and I try to commit again. Some files are now in the repository
but still scheduled for addition in the local copy. (A clean doesn't
cancel these additions.) An update of the repository doesn't help since
no other user accessed the repository in the meanwhile.
I thought, it could never happen that some files of one commit are added
while others aren't since in case of an error the transaction is rolled
This issue has nothing to do with the case insensitivity problem with
Windows file names.
The only thing I can do to synchronize my local copy and the repo is to
rename the directory of the local copy that contains the problem, check
out the directory again, copy the changes/new files to the new directory
and then add+commit again.

I'm sorry that I can't currently tell you how to reproduce the error. I
don't seem the first who had this problem.

Shouldn't SVN be able to recognize an out of sync (files scheduled for
addition already exist) and repair it (cancel/revert scheduled addition
and consider files as up to date (perhaps after a validation))?

I'm using svn 1.3.1 and TortoiseSvn on Win2003/XP. The
repository is accessed by svn:// and is an FSFS.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri May 5 10:43:17 2006

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.