This issue is caused by a bug in the current capistrano-git bridge. It's been fixed (here: http://github.com/jamis/capistrano/commit/15e9ed54d8b2db039fbe7dd76413ad92db40fb9a) , and if you want the fix without waiting for the next release, you can grab this file (http://github.com/jamis/capistrano/tree/15e9ed54d8b2db039fbe7dd76413ad92db40fb9a/lib/capistrano/recipes/deploy/scm/git.rb ) and drop it in capistrano/recipes/deploy/scm/git.rb in your gem directory.

- Jamis

On May 15, 2008, at 8:37 PM, Alan Harper wrote:


On Tue, May 6, 2008 at 10:22 AM, Will <[EMAIL PROTECTED]> wrote:

Seeing that same error myself.  I was able to get around it by
commenting out set :remote_cache true from my config/deploy.rb

On May 4, 9:30 am, BadMinus <[EMAIL PROTECTED]> wrote:
After i run "cap deploy" and other commands capistrano give me this
error

** [err] fatal: Could not parse object
'357503cfc0bcfc1364b87732b40ee68fff7599c5'.
I'm having the same issue here. I manually logged in to the server,
and ran "git pull origin production", which pulled the missing git
object and allowed the deploy to continue. Still gitting the hang of
git, otherwise I'd have already started on the patch

--~--~---------~--~----~------------~-------~--~----~
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/capistrano
-~----------~----~----~----~------~----~------~--~---


Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to