Hg TortoiseHg error in window 7

Question

I am cloning a new repository from TortoiseHg version 2.1.3. Then make some change. When I do a commit, I get this message as shown below.

The display of my working disk is connected to the Linux Samba server.

I really appreciate if anyone 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% 

Answer 1

For me, changing the setting:

 Global Settings -> TortoiseHg -> Monitor Repo Changes 

to

 localonly 

helped.

A lengthy discussion in the official bug tracker: https://bitbucket.org/tortoisehg/thg/issue/889/

Answer 2

I saw the same problem, but I noticed that "sometimes" I can make changes. I think the “other process” is something on the server.

When I cannot commit, hg gives the error message (among other things) "interrupt transaction failed!" - run hg recovery ".

If I run hg recovery, sometimes it will not work either (used by another process). If I wait a minute or two, try again to return, this often succeeds.

Once the recovery is successful, if I wait another minute or two, then the commit is often performed when I repeat it.

My theory is that the server indexes or scans for viruses the contents of .hg /

---

I don’t know the guaranteed operation, but in my small repository I can often enter my inserts if I give it a try or two. The likelihood of your luck will increase as the activity of your repository files decreases.

Answer 3

I do not know about the commit , but I know that Mercurial / TortoiseHG has problems when you click on the Linux disk that appears under Windows. p>

See these answers that I wrote about this:

• Mercury remote controls in the file system instead of the http server
• Can you "click" on a network resource using Mercurial on 64-bit Windows 7?

Perhaps the same problems occur when the repository you are trying to transfer is directly on the mapped Linux drive.

I would advise placing the repository on a real Windows disk and trying if you can commit it.
If so, the problems you described are probably due to a Linux drive.