What's on line 1 of config/deploy.rb? The require there seems to be
triggering this.

- Jamis

On 9/21/07, mike b. <[EMAIL PROTECTED]> wrote:
>
> Hi all!
>
> I run Rails under OS X and I finally have an app that I want to deploy
> and yet Capistrano is not playing along and gives me this error:
>
> $ cap install_rails_stack_with_nginx
> /usr/local/lib/ruby/site_ruby/1.8/rubygems.rb:246:in `activate': can't
> activate capistrano (= 1.4.1), already activated capistrano-2.0.0]
> (Gem::Exception)
>         from /usr/local/lib/ruby/site_ruby/1.8/rubygems.rb:264:in
> `activate'
>         from /usr/local/lib/ruby/site_ruby/1.8/rubygems.rb:263:in
> `each'
>         from /usr/local/lib/ruby/site_ruby/1.8/rubygems.rb:263:in
> `activate'
>         from /usr/local/lib/ruby/site_ruby/1.8/rubygems/
> custom_require.rb:31:in `require'
>         from /usr/local/lib/ruby/gems/1.8/gems/capistrano-2.0.0/lib/
> capistrano/configuration/loading.rb:85:in `require'
>         from ./config/deploy.rb:1:in `load'
>         from /usr/local/lib/ruby/gems/1.8/gems/capistrano-2.0.0/lib/
> capistrano/configuration/loading.rb:97:in `load_from_file'
>         from /usr/local/lib/ruby/gems/1.8/gems/capistrano-2.0.0/lib/
> capistrano/configuration/loading.rb:66:in `load'
>          ... 13 levels...
>         from /usr/local/lib/ruby/gems/1.8/gems/capistrano-2.0.0/lib/
> capistrano/cli/execute.rb:14:in `execute'
>         from /usr/local/lib/ruby/gems/1.8/gems/capistrano-2.0.0/bin/
> cap:4
>         from /usr/local/bin/cap:16:in `load'
>         from /usr/local/bin/cap:16
>
>
> I tried removing /usr/local/lib/ruby and downloading rubygems again
> and installing all gems all over again and I get the same error.
>
> Could someone please help and point me in the right direction?
>
> Thank you!
>
> Mike
>
>
> >
>

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

Reply via email to