Mercurial strangeness

[Phil]

I have a Mercurial repository on my laptop which I clone locally to
make code changes, these changes are committed locally and
periodically groups of changes are pushed back into the 'master'
repository. This works well.

Last night I set up a new clone of the repository on a NAS drive. My
Mac automatically reconnects to the NAS drive when I log in. The NAS
repository will be accessed by a Hudson installation on another Mac on
the network to build and deploy into a sandbox, so that the current
working version of the application is always available to play with.

Having set up the repository in the normal manner (hg clone) last
night I've tried to push changes to it today, only to receive the
following message:

pushing to /Volumes/mercurial/content-api
abort: No such file or directory: /Volumes/mercurial/content-api/.hg/
store/lock

And yes, looking in /Volumes/mercurial/content-api/.hg/store, there is
no file or directory called 'lock'. Any suggestions?

[Peter Becker]

I don't think there should be such a file unless hg is working. If this
question is Java related at all, you might suffer from the infamous
exception reuse problems in the JDK. In this case the overloaded
FileNotFoundException could be the culprit. Maybe your problem is a lack
of a write permission on the folder, not the lack of the file.

Peter