Can you "click" on a network resource using Mercurial on 64-bit Windows 7?

Question

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

We currently store Mercurial central repositories on a network share, clone copies to our workstations, and push our changes back to network storages. This works fine in WinXP, but in Win7 I consistently get an error message when returning to a network resource:

clicking on 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 '

I am using TortoiseHG 1.1.1 and Mercurial 1.6.1023.

I managed to click on repositories stored on the same workstation, but not on the repo. If possible, we would prefer not to visit the web server-based repository - this is a struggle to ensure that new software is added to our servers.

Answer 1

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

See the “shared drive” section in Publishing Repositories to the Mercurial Wiki:

usually limited to intranets, not usually recommended due to a common problem with the network file system

At my workplace, we store our HG repositories on a network share (on a Windows 2003 server), as it was easiest to configure. We do this for about a year and a half, and we have never had such problems as yours.

But at home I have a network share on the NAS (it is accessible from Windows, and it looks and looks like a Windows share, but the NAS actually works on Linux). I have not had problems for a long time, but from a few weeks I had similar errors like you (with another error message).
I posted this on the Mercurial bug tracker , and I was told that my problem was probably due to the fact that my NAS runs on Linux because they do not know any problems with real Windows shares:

On real Windows promotions (served by Windows), there seems to be no problem (I've never heard of other problems with this).

So maybe your problem is caused by something similar. What proportion of Windows are you trying to click? Is it really on a windows machine?