Hey Rob, that's working... but what's it doing? :-) I'll keep an eye on this as various gems get updated and I am more rigorous in my applying of those updates.
I'm off to read more of the bundler documentation... On Mar 20, 6:35 pm, Rob Biedenharn <[email protected]> wrote: > Have you tried to run as: > > bundle exec cap deploy:update > > That would tell you if it's a system v. rvm gems thing. > > -Rob > > On Mar 20, 2011, at 7:27 PM, Jim wrote: > > > > > I spoke too soon. I figured the best test was to immediately try a > > normal workflow after updating to RubyGems 1.6.2. > > > Well "bundle install" gave a lot of the usual "using..." messages, but > > then it:' > > > Installing net-ssh (2.1.0) > > Installing net-scp (1.0.4) > > Installing net-sftp (2.0.5) > > Installing net-ssh-gateway (1.0.1) > > Installing capistrano (2.5.20) > > > Which is a little interesting because I had just done that, but under > > RubyGems 1.6.0. And I noticed that net-ssh was a step backwards, > > because the previously installed version was 2.1.3 (I needed only > > scroll back a bit in my terminal window to verify that). > > > And alas, an attempt: > > > cap deploy:update > > > errored again that you can't activate net-ssh (=2.0.4) when we've > > already activated net-ssh-2.1.0 > > > So for completeness for others who might be searching the Internet for > > help with a similar problem, I just updated RubyGems as sudo... > > > sudo gem update --system > > > RubyGems installed the following executables: > > /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/gem > > > and I was able to cap deploy:update once again. > > > So I'm left with an impression that cap is using the system libraries > > and not the "closer" rvm versions. > > > Probably I'll be the next one to "discover" this when searching again > > in the future after I forget all this! > > > On Mar 20, 4:06 pm, Jim <[email protected]> wrote: > >> Well, I just say RubyGems 1.6.2 says: > > >> Installing RubyGems 1.6.2 > >> RubyGems 1.6.2 installed > > >> === 1.6.2 / 2011-03-08 > > >> Bug Fixes: > > >> * require of an activated gem could cause activation conflicts. > >> Fixes > >> Bug #29056 by Dave Verwer. > > >> So maybe you don't need to throw out jeweler! > > >> On Mar 20, 3:19 pm, Lee Hambley <[email protected]> wrote: > > >>> Jim, > > >>> Sorry - have been off-line for a couple of days (visiting family > >>> abroad) > >>> Glad you found a fix, this is the 2nd report of dodgy dependencies > >>> in the > >>> Jeweler generated gemfile, I'll be throwing Jeweler out, and > >>> version-controlling a Gemfile as a matter or urgency on return > >>> from my > >>> vacation, as the whole thing is a little too opaque for me. > > >>> Lee > > > -- > > * You received this message because you are subscribed to the Google > > Groups "Capistrano" group. > > * To post to this group, send email to [email protected] > > * To unsubscribe from this group, send email to > > [email protected] > > For more options, visit this group > > athttp://groups.google.com/group/capistrano?hl=en -- * You received this message because you are subscribed to the Google Groups "Capistrano" group. * To post to this group, send email to [email protected] * To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/capistrano?hl=en
