No subject

cleanup.  Also, if I understand the code correctly, this is an
annoyance to you rather than a crash, right?  I mean, you're still
getting the 'status' output and can still get things done?

> It looks like it might be permissions, but everything seems alright.
>
> Mercurial v 1.2
> Windows XP SP2
> Repo is sitting on a NAS box running busybox.

Have you tried cloning the repo to the local disk and working there?

Have you tried logging into the NAS and using hg there?  Not for
everyday use, of course, just to test if the problem still happens
there.

Have you tried accessing the NAS from a different client, especially
one running a different OS?

You might try running "hg --debug --traceback status" to see if you
get more details about the error.  I don't *think* it'll help, but it
costs nothing to try.

Finally, you might try the latest development version of Mercurial:
the way locks are released has been cleaned up, and errors like this
might be reported better.  (I think.)  To do that, clone
http://hg.intevation.org/mercurial/crew and ... oh wait.  I don't know
how to build Mercurial on Windows.  Well, try the above suggestions
first and see if any of them help.

Greg