Infinite lock wait loop when working copy does not exist

[blee]

blee@… ~ $ confman commit
confman[34533]: blee: cat: /home/blee/src/conf/confman.lock: No such file or directory
confman[34533]: blee: waiting for lock on /home/blee/src/conf/confman.lock...
confman[34533]: blee: cat: /home/blee/src/conf/confman.lock: No such file or directory
confman[34533]: blee: waiting for lock on /home/blee/src/conf/confman.lock...
[...]
^{CPlease wait until I finish cleaning up after you.}

[ccowart]

Looks like I corrected this issue in conflock in revision 401, possibly
without realizing it addressed this ticket.

conflock now has sanity checking to ensure that the lockfile's parent
directory indeed exists.

Leaving open so this fix can be merged into the 1.9 branch.

[ccowart]

(In [410]) So just fixing locking wasn't quite enough; the error message to the user
was quite confusing the case that the wcopy didn't exist.

I added a check for the existence of the wcopy. This gets called within
the lock function.

Still pending merge to 1.9 (which I'm testing right now).

See #47

[ccowart]

(In [412]) Merging fixes from trunk for several issues.

Fixes #49, #53, #61, #47, #48