I believe that this commit caused this behavior: http://github.com/jamis/capistrano/commit/ec9a7fa52c9f417a9a01a7e764b520be1ec32c5c
I'm trying to think of a workaround, but it comes down to a different philosophy about where the knowledge of the repository should live. It's either old way: machine issuing cap command knows new way: machines doing the code check out know On Fri, Jun 13, 2008 at 1:44 PM, H. Wade Minter <[EMAIL PROTECTED]> wrote: > > I'm deploying a Rails app to the same server that houses the git > repository. I'm trying to use this in my deploy.rb: > > set :scm, :git > set :repository, "file:///usr/local/git/carpool.git" > set :deploy_via, :remote_cache > set :branch, "master" > set :repository_cache, "git_cache" > set :use_sudo, false > > In Capistrano 2.2, this works fine. However, in 2.3 and the just- > released 2.4, I get: > > * executing `deploy:update_code' > updating the cached checkout on all servers > fatal: '/usr/local/git/carpool.git': unable to chdir or not a git > archive > fatal: The remote end hung up unexpectedly > *** [deploy:update_code] rolling back > * executing "rm -rf /usr/local/www/carpool/releases/20080613174107; > true" > servers: ["10.5.88.49"] > [10.5.88.49] executing command > command finished > /Library/Ruby/Gems/1.8/gems/capistrano-2.4.0/lib/capistrano/recipes/ > deploy/scm/git.rb:217:in `query_revision': Unable to resolve revision > for 'master' on repository 'file:///usr/local/git/carpool.git'. > (RuntimeError) > from /Library/Ruby/Gems/1.8/gems/capistrano-2.4.0/lib/capistrano/ > recipes/deploy/scm/base.rb:35:in `send' > > > Is there a workaround or anything for this? Or are file:// repository > URLs no longer supported? > > > --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
