The gem assumes a single (deploy) user, and will fail if that is not the case and someone else has a lock with:
$ cap deploy HOSTS=
*** [err :: ] chmod: changing permissions of
`/capistrano.lock.yml': Operation not permitted
failed: "sh -c 'chmod 777 /capistrano.lock.yml'" on
It also seems strange that a log file has execute permissions, i.e. should be 666.
The gem assumes a single (deploy) user, and will fail if that is not the case and someone else has a lock with:
$ cap deploy HOSTS=
*** [err :: ] chmod: changing permissions of
`/capistrano.lock.yml': Operation not permitted
failed: "sh -c 'chmod 777 /capistrano.lock.yml'" on
It also seems strange that a log file has execute permissions, i.e. should be 666.