Splitting this out from issue2720:

For issue2333, we get:

> darcs: security: createProcess: posix_spawnp: does not exist (No such file 
or directory)

The problem seems to be that darcs, or probably some library it
calls or the OS, is trying to invoke a binary called 'security',
which lives in /usr/bin.

This goes wrong in this line:

> PATH='' $thedarcs push ../S -a

Changing the line to `PATH='/usr/bin' ...` fixes the test.

I need to do some more digging to understand how this is supposed
to fit together and what the best thing for the test is.

I believe this is really the same problem as issue2720. In 
tests/issue1465_ortryrunning.sh we also set the PATH, like this:

PATH=.:$DARCSDIR \
darcs record    -lam 'Initial commit.' --edit </dev/null &> log-2

(This is nothwithstanding the fact that this test is slightly broken in 
that it should be PATH=..:$DARCSDIR; and that we could as well change it 
to PATH=..:$PATH to /avoid/ the issue.)

ah yes, putting /usr/bin in the PATH in issue1465_ortryrunning.sh also
fixes that. I'll move the discussion back to issue2720.