无法在 Mac 上使用 beanstalk 提交到 svn
我使用 Xcode 3.2、Mac OS 10.6 和 svn 进行版本控制。我在这个 svn 中使用 beanstalk。我在 beanstalk 中创建了一个存储库并在 Xcode 中进行了更改。当我尝试从 SCM 提交项目时，出现以下错误：
错误：155005（工作副本未锁定；这可能是一个错误，请报告）描述：提交失败（详细信息如下）：
错误：155005（工作副本未锁定；这可能是一个错误，请报告）描述：目录'/Users/Mango3/Documents/Dropbox/splitview/SplitView 2-1 3 2 2/build/SplitView.build/SplitView.pbxindex ' 缺失
错误：155010（找不到工作副本路径）说明：目录“/Users/Mango3/Documents/Dropbox/splitview/SplitView 2-1 3 2 2/build/SplitView.build/SplitView.pbxindex”丢失
我有浏览了很多论坛，但我仍然面临同样的问题。我应该怎么办？
I am using Xcode 3.2, Mac OS 10.6 and svn for version control. I am using beanstalk for this svn. I created a repository in beanstalk and made changes in Xcode. When I tried to commit the project from SCM, I got this error:
Error: 155005 (Working copy not locked; this is probably a bug, please report) Description: Commit failed (details follow):
Error: 155005 (Working copy not locked; this is probably a bug, please report) Description: Directory '/Users/Mango3/Documents/Dropbox/splitview/SplitView 2-1 3 2 2/build/SplitView.build/SplitView.pbxindex' is missing
Error: 155010 (Can't find a working copy path) Description: Directory '/Users/Mango3/Documents/Dropbox/splitview/SplitView 2-1 3 2 2/build/SplitView.build/SplitView.pbxindex' is missing
I have gone through many forums, but I am still facing the same problem. What should I do?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
你也许应该和 Beanstalk 谈谈这件事。
您可以尝试的一件事（相当于“重新启动您的电脑”:) 是删除本地副本，然后再次检查。当然，请确保将本地更改保存在安全的地方。然后复制并将这些更改粘贴回。
You should probably talk to Beanstalk about this.
One thing you can try (it's equivalent to "restart your PC" :) is deleting the local copy, and check it out again. Make sure you keep your local changes safe somewhere, of course. Then copy & paste those changes back in.
在经历备份更改和清除工作副本的麻烦之前，请尝试运行 svn cleanup 命令。有时，工作副本只是自我封闭。
Before going through the trouble of backing up your changes and blowing away your working copy, try running the svn cleanup command. Sometimes working copies just get wrapped up on themselves.