Xcode和SCM冲突错误

发布于 2024-08-05 11:26:35 字数 246 浏览 6 评论 0原文

尽管我是唯一从事该项目的人,但我收到以下错误。

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

为什么会发生这种情况,因为我一直在做的就是每次在进行一些认真的编码之前提交项目。我已经提交了三次,现在它不允许再提交了,因为它会抛出该错误。

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.

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(3

轻许诺言 2024-08-12 11:26:35

好吧,大家,这里是解决这个问题的具体方法,假设您的文件具有当前最新版本:

prompt$ svnresolve --acceptworkingyourfilenamehere

Resolvedconflictedstateofyourfilenamehere

然后检查通常从 xcode GUI 中。就是这样!

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!

扛起拖把扫天下 2024-08-12 11:26:35

你有一个冲突需要在 svn 中解决。如果不是其中一个文件,请检查是否是树冲突。

来自 SVN 1.6 发行说明

Subversion 1.6 识别出一种新的冲突,称为“树冲突”。这种冲突体现在目录结构级别,而不是文件内容级别。

现在标记为冲突的情况包括删除本地修改的文件以及对本地删除的文件进行传入编辑。在冲突标记为已解决之前,无法提交受树冲突影响的文件和目录。

请注意,Subversion 仍然将重命名视为“复制+删除”操作,因此只能通过文件添加和删除来检测导致树冲突的文件重命名。因此,树冲突检测期间可能出现误报。

为了促进树冲突检测,尝试提交删除已在 HEAD 修订版中删除的文件现在会导致错误。在 Subversion 1.5 中,这被视为无操作,可能会导致不包含任何更改的“空”修订版。

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.

软糯酥胸 2024-08-12 11:26:35

另一种解决方案是使用可视化客户端,例如 Versions 并从菜单中选择“解决冲突”,这似乎适用于上述和其他解决技术。

Another solution is to use a visual client such as Versions and choose "resolve conflicts" from the menu, which seems to apply the above and other resolution techniques.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文