[Capistrano] Re: Upgrading to Cap2, conflict with old version, 1.4.1

[Jamis Buck]

In the past, this has happened because the deprec gem (which does not work with 2.0) is being loaded. Check your deploy.rb and make sure you aren't requiring the deprec gem anywhere. Also, you might want to check ~/.caprc, since some people have been loading deprec there.

- Jamis

On Oct 12, 2007, at 6:10 AM, Kris wrote:

/usr/local/lib/site_ruby/1.8/rubygems.rb:246:in `activate': can't
activate capistrano (= 1.4.1), already activated capistrano-2.0.0]
(Gem::Exception)


I just upgraded to Capistrano 2, but there seems to be a conflict with
my old version, how do I choose which gem to use?

Any suggestions please.


--~--~---------~--~----~------------~-------~--~----~

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

-~----------~----~----~----~------~----~------~--~---

smime.p7s
Description: S/MIME cryptographic signature