views:

979

answers:

2

I am getting this following error even though i am the only person working on this project.

> Error: 155015 (A conflict in the working copy obstructs the current operation) Description: Commit failed

why would this occur as all i keep doing is committing the project every time before do some serious coding. I have committed three times now it is not allowing any more as it throws that error.

+2  A: 

You've got a conflict that needs to be resolved in svn. If it's not one of the files, check if it's a tree conflict.

From the SVN 1.6 release notes:

Subversion 1.6 recognizes a new kind of conflict, known as a "tree conflict". Such conflicts manifest at the level of directory structure, rather than file content.

Situations now flagged as conflicts include deletions of locally modified files, and incoming edits to locally deleted files. Files and directories which are victims of a tree conflict cannot be committed before the conflict is marked resolved.

Note that Subversion is still treating renames as a "copy+delete" operation, so file renames causing tree conflicts can only be detected in terms of file additions and deletions. Because of this, false positives during tree conflict detection are possible.

To facilitate tree conflict detection, attempting to commit the deletion of a file which has already been deleted in the HEAD revision now causes an error. In Subversion 1.5, this was treated as a no-op, potentially resulting in "empty" revisions which contained no changes.

Terry Wilcox
Snow Leopard now comes with version 1.6, where Leopard came with 1.4, so he might be hitting this if he just upgraded.
Brad Larson
+1  A: 

Ok everyone, here's precisely how to solve this problem, assuming your file has the current latest version:

prompt$ svn resolve --accept working yourfilenamehere

Resolved conflicted state of yourfilenamehere

Then check in normally from the xcode GUI. That's it!

sss