您可以在64位Windows 7上使用Mercurial“推送"网络共享吗? [英] Can you 'push' to network share using Mercurial on 64bit Windows 7?

问题描述

我们正在从Windows XP x86升级到Windows 7 x64的过程中，并且我正在测试当前工作流程的兼容性问题.

We are in the process of upgrading from Windows XP x86 to Windows 7 x64, and I'm testing for compatibility problems with our current workflow.

当前，我们将中央Mercurial存储库存储在网络共享上，将副本克隆到我们的工作站，并将更改推回到基于网络的存储库中.这在WinXP中可以完美运行，但是在Win7中，当我推回网络共享时始终会收到错误消息:

Currently, we store central Mercurial repositories on a network share, clone copies to our workstations, and push our changes back to the network-based repositories. This works perfectly in WinXP, but in Win7 I consistently get an error message when pushing back to the network share:

推送至t:\ datamgt \ automat \ Kevin \ SampleRepo 寻找变化 [错误32]该进程无法访问文件，因为该文件正在被另一个进程使用:'T:\ datamgt \ automat \ Kevin \ SampleRepo \ .hg \ journal.dirstate'

pushing to t:\datamgt\automat\Kevin\SampleRepo searching for changes [Error 32] The process cannot access the file because it is being used by another process: 'T:\datamgt\automat\Kevin\SampleRepo\.hg\journal.dirstate'

我正在使用TortoiseHG 1.1.1和Mercurial 1.6.1023.

I'm using TortoiseHG 1.1.1 and Mercurial 1.6.1023.

我已经可以推送到存储在同一工作站上的存储库，但不能推送到网络共享存储库.如果可能的话，我们宁愿不要使用基于Web服务器的存储库-将新软件添加到我们的服务器是一项艰巨的任务.

I've been able to push to repositories stored on the same workstation, but not to the network share repo. If possible, we'd prefer not to go to a webserver-based repository - it's an up-hill fight to get new software added to our servers.

推荐答案

可以推送到网络共享，但Mercurial团队不建议这样做.

Pushing to a network share is possible, but not recommended by the Mercurial team.

请参阅Mercurial Wiki中发布存储库中的共享磁盘"部分:

See the "shared disk" part in Publishing Repositories in the Mercurial wiki:

通常仅限于Intranet，不 一般建议 网络文件系统问题 可靠性

generally restricted to intranets, not generally recommended due to general issues with network filesystem reliability

在我的工作场所中，我们也将HG存储库也保存在网络共享(在Windows 2003服务器上)上，因为它最容易设置.我们已经进行了大约一年半的时间，而且从未遇到过像您这样的问题.

At my workplace, we are keeping our HG repositories on a network share (on a Windows 2003 server) as well because it was the easiest to set up. We're doing this for about one and a half year now, and we never had problems like yours.

但是在家里，我在NAS上有一个网络共享(可以从Windows进行访问，它看起来和感觉像Windows共享，但是NAS实际上在Linux上运行).我很长一段时间都没遇到问题，但是由于几个星期以来，我遇到了类似您的类似错误(尽管有不同的错误消息).
我将其发布在Mercurial错误跟踪器上，并被告知我的问题可能是由我的NAS在Linux上运行的事实，因为他们不知道 real Windows共享的任何问题:

But at home, I have a network share on a NAS (it's accessible from Windows and it looks and feels like a Windows share, but the NAS actually runs on Linux). I had no problems for a long time, but since a few weeks I'm having similar errors like you (with a different error message though).
I posted this on the Mercurial bug tracker, and I was told that my problem is probably caused by the fact that my NAS runs on Linux, because they don't know of any problems with real Windows shares:

在实际的Windows共享上(由 Windows)似乎没有 问题(从未听说过其他人有 这样做的问题).

On real Windows shares (served by Windows) there doesn't seem to be a problem (never heard of others having problems doing that).

所以也许您的问题也是由类似原因引起的.
您尝试使用哪种Windows共享?真的在Windows机器上吗?

So maybe your problem is caused by something similar as well.
What kind of Windows share is it that you try to push to? Is it really on a Windows machine?

这篇关于您可以在64位Windows 7上使用Mercurial“推送"网络共享吗?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！