Michaël, happy to agree with you that this is a bug, very few people in my experience use deploy:check - however it's a trivial change (for us guys who know where that code is!) to make sure it honours the admin runner, or sudo privileges.
Take the issue to Lighthouse, or to the Github Capistrano tracker (transition phase at the moment, so I'll pick it up in either place) - Lee -- * 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
