Windows 7 上的 Hg TortoiseHg 提交错误
我通过 TortoiseHg 版本 2.1.3 克隆了一个新存储库。然后做一些改变。当我提交时，我收到如下消息。
我的桌面驱动器映射通过 Samba 连接到 Linux 服务器。
如果有人可以提供帮助，我非常感激。
% hg commit --repository V:\htdocs\critical\mysite2 --verbose --user MyUser --message=testing Mercuial V:\htdocs\critical\mysite2/application/controllers/package.php
smartdox/application/controllers/package.php
transaction abort!
rollback completed
abort: The process cannot access the file because it is being used by another process
[command returned code 255 Fri Jan 13 14:30:17 2012]
mysite2%
I clone a new repository by TortoiseHg version 2.1.3. Then do some change. When I do commit, I get this message as below.
My desktop drive mapping is connected to Linux server by Samba.
I am so appreciate if someone can help.
% hg commit --repository V:\htdocs\critical\mysite2 --verbose --user MyUser --message=testing Mercuial V:\htdocs\critical\mysite2/application/controllers/package.php
smartdox/application/controllers/package.php
transaction abort!
rollback completed
abort: The process cannot access the file because it is being used by another process
[command returned code 255 Fri Jan 13 14:30:17 2012]
mysite2%
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
对我来说改变设置：
有
帮助。
官方错误跟踪器中的长时间讨论：https://bitbucket.org/tortoisehg/thg/issue/889/
For me changing the setting:
to
helped.
The long discussion in the official bug tracker: https://bitbucket.org/tortoisehg/thg/issue/889/
我也见过同样的问题，但我注意到“偶尔”我能够提交更改。我认为“另一个进程”是服务器上的东西。
当我未能提交时，hg 会给出一个错误（除其他外）“事务中止！回滚失败 - 请运行 hg 恢复”。
如果我运行 hg recovery，有时也会失败（被另一个进程使用）。如果我等待一两分钟，然后重试恢复，通常会成功。
一旦恢复成功，如果我再等待一两分钟，那么当我重试时，提交通常会成功。
我的理论是，服务器正在对 .hg/ 的内容进行索引或病毒扫描，
我不知道有保证的解决方法，但在我的小型存储库上，如果我尝试一两次，我通常可以获取更改集。随着存储库文件的活动减少，您的运气可能会增加。
I've seen this same problem, but I've noticed that "occasionally" I am able to commit changes. I think the 'another process' is something on the server.
When I fail to commit, hg gives an error saying (among other things) "transaction abort! rollback failed - please run hg recover".
If I run hg recover, sometimes that fails, too (in use by another process). If I wait a minute or two, then retry to recover, it often succeeds.
Once the recovery succeeds, if I wait another minute or two, then the commit often succeeds when I retry it.
My theory is that the server is indexing or virus-scanning the contents of .hg/
I don't know a guaranteed work-around, but on my small repository I can often get my changesets in if I give it a try or two. Your luck is likely to increase as the activity on your repository files decreases.
我不太了解提交，但我知道当您推送到 Windows 下映射的 Linux 驱动器时，Mercurial/TortoiseHG 会出现问题。
请参阅我写的有关它的这些答案：
当您尝试提交的存储库直接驻留在映射的 Linux 驱动器上时，可能会出现相同的问题。
我建议您将存储库放在真正的 Windows 驱动器上，并尝试是否可以在那里提交。
如果是的话，您所描述的问题可能是由于Linux驱动引起的。
I don't really know about committing, but I know that Mercurial/TortoiseHG has issues when you push to a Linux drive which is mapped under Windows.
See these answers I wrote about it:
Maybe the same problems occur when the repository you're trying to commit to directly resides on a mapped Linux drive.
I'd suggest that you put the repository on a real Windows drive and try if you can commit there.
If yes, the problems you described are probably because of the Linux drive.