On Tue, 17 Jul 2012 17:09:48 +0100, A. S. Budden wrote: > We recently started using Mercurial for version control within our > company. Most people use their local hard drive for the working > directory (and use Microsoft SyncToy to ensure that un-pushed changes > are backed up on the network drive). However, our department manager > prefers to work on the network drive all of the time. He has been > having a lot of problems with TortoiseHG: most times he tries to pull > he gets something like this: > > % hg --repository F:\Working directory pull --verbose F:\VCS\Project > pulling from F:\VCS\Project > searching for changes > 2 changesets found > adding changesets > adding manifests > adding file changes > added 2 changesets with 2 changes to 1 files (+1 heads) > transaction abort! > rollback completed > abort: The process cannot access the file because it is being used > by another process > [command returned code 255 Tue Jul 17 16:57:26 2012] [...] > > Has anyone experienced this? Are there any known work-arounds?
Using local drive is the best solution, but probably you can work around this error by disabling file-system monitoring: https://bitbucket.org/tortoisehg/thg/issue/889/#comment-993231 Regards, ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Tortoisehg-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tortoisehg-discuss
