"can't activate net-ssh" in Capistrano

110 views
Skip to first unread message

Fjan

unread,
Mar 3, 2011, 5:31:11 AM3/3/11
to gemcutter
After upgrading to RubyGems 1.6.0 I get this error when I try to
deploy:

/Library/Ruby/Site/1.8/rubygems.rb:267:in `activate': can't activate
net-ssh (= 2.0.4) for [], already activated net-ssh-2.1.3 for []
(Gem::LoadError)

It works fine again when I downgrade to RubyGems 1.5.3. "bundle
install" / "bundle update" is not helping. Anybody have a clue what
could be causing that?

Fjan

unread,
Mar 20, 2011, 9:00:05 AM3/20/11
to gemcutter
RubyGems 1.6.2 seems to fix this...

Jim

unread,
Mar 19, 2011, 10:33:30 PM3/19/11
to gemcutter
I'm getting the same error. I actually got my gems aligned once to
get around this, but today, after a "bundle install" I'm back to this
error.

For the purposes of comparing notes:

rvm version 1.2.8
GEM_HOME and GEM_PATH are unset

I'm using ruby 1.8.7 patchlevel 174, but have 3 generations of 1.9.2
installed, which I'm not using in this situation

gem list capistrano shows version 2.5.20 is my current version, with
versions 2.5.19 and 2.5.2 hanging out there.

Similarly,

gem list net- shows

net-scp (1.0.4, 1.0.1)
net-sftp (2.0.5, 2.0.1, 1.1.1)
net-ssh (2.1.3, 2.0.4, 1.1.4)
net-ssh-gateway (1.0.1, 1.0.0)

The rvm equivalents provide:

rvm gem list capistrano

*** LOCAL GEMS ***

capistrano (2.5.20, 2.5.19)

*** LOCAL GEMS ***

capistrano (2.5.20)

*** LOCAL GEMS ***

capistrano (2.5.20, 2.5.19)

*** LOCAL GEMS ***

capistrano (2.5.20, 2.5.19)

and the net- situation is:

rvm gem list net-

*** LOCAL GEMS ***

net-scp (1.0.4)
net-sftp (2.0.5)
net-ssh (2.1.3, 2.0.4)
net-ssh-gateway (1.0.1)

*** LOCAL GEMS ***

net-scp (1.0.4)
net-sftp (2.0.5)
net-ssh (2.1.3, 2.0.4)
net-ssh-gateway (1.0.1)

*** LOCAL GEMS ***

net-scp (1.0.4)
net-sftp (2.0.5)
net-ssh (2.1.3, 2.0.4)
net-ssh-gateway (1.0.1)

*** LOCAL GEMS ***

net-scp (1.0.4)
net-sftp (2.0.5)
net-ssh (2.1.3, 2.0.4)
net-ssh-gateway (1.0.1)

I tried simply uninstalling net-ssh --version='2.1.3' but this version
of capistrano is looking for a more recent version than 2.0.4

If I fiddle around enough to conclusively know what I did that fixes
this, I'll post back!
Reply all
Reply to author
Forward
0 new messages