I'd try and rule out anything like ey-cap, and reduce it to your basic
connection things, the idea that this has been raised before you even made a
connection highlights that there's probably something up with some pre-setup
code.
This is also suspicious:
# This will execute the Git revision parsing on the *remote* server rather
> than locally
set :real_revision, lambda { source.query_revision(revision) { |cmd|
> capture(cmd) } }
There isn't usually a need to do that, but OK!
Also, in times like this, clearing the remote cache is always a smart move -
but I'm not sure this qualifies :-D (since you're not even getting on the
server for that to be making problems
-- Lee Hambley
Twitter: @leehambley | @capistranorb
--
* You received this message because you are subscribed to the Google Groups
"Capistrano" group.
* To post to this group, send email to [email protected]
* To unsubscribe from this group, send email to
[email protected] For more options, visit this group at
http://groups.google.com/group/capistrano?hl=en
