Databases
StackOverflow2013
Postsdbo
POHow do I get `gem` working again after upgrading to rubygems 1.8.x?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POHow do I get `gem` working again after upgrading to rubygems 1.8.x?
    primarykey
    data
    text
    <p>Soooo, I upgraded to RubyGems 1.8.1 from 1.7.2 using <code>gem upgrade --system</code>, then immediately ran <code>gem pristine --all --no-extensions</code> as recommended on <a href="http://blog.segment7.net/2011/05/04/rubygems-1-8-0" rel="nofollow">Eric Hodel's blog</a>. After getting errors when running <code>gem</code> commands, I googled around a bit, found some suggestions to <code>gem uninstall</code> the gems with the deprecation warnings, but then realized I can't, as <code>gem uninstall</code> just errors out--as does any other command--including just plain ol' <code>gem</code>.</p> <p>When I run any of those commands, I get a bunch of "deprecated" warnings still, then this backtrace:</p> <pre><code>/Users/sloveless/.rvm/rubies/ruby-1.9.2-p180/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:277:in `block in _resort!': undefined method `name' for nil:NilClass (NoMethodError) from /Users/sloveless/.rvm/rubies/ruby-1.9.2-p180/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:276:in `sort!' from /Users/sloveless/.rvm/rubies/ruby-1.9.2-p180/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:276:in `_resort!' from /Users/sloveless/.rvm/rubies/ruby-1.9.2-p180/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:270:in `_all' from /Users/sloveless/.rvm/rubies/ruby-1.9.2-p180/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:402:in `each' from /Users/sloveless/.rvm/rubies/ruby-1.9.2-p180/lib/ruby/site_ruby/1.9.1/rubygems.rb:477:in `map' from /Users/sloveless/.rvm/rubies/ruby-1.9.2-p180/lib/ruby/site_ruby/1.9.1/rubygems.rb:477:in `find_files' from /Users/sloveless/.rvm/rubies/ruby-1.9.2-p180/lib/ruby/site_ruby/1.9.1/rubygems.rb:1061:in `load_plugins' from /Users/sloveless/.rvm/rubies/ruby-1.9.2-p180/lib/ruby/site_ruby/1.9.1/rubygems/gem_runner.rb:85:in `&lt;top (required)&gt;' from /Users/sloveless/.rvm/rubies/ruby-1.9.2-p180/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /Users/sloveless/.rvm/rubies/ruby-1.9.2-p180/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /Users/sloveless/.rvm/rubies/ruby-1.9.2-p180/bin/gem:9:in `&lt;main&gt;' </code></pre> <p>The same thing happened when I tried this again, but upgrading from RubyGems 1.6.2, using the same update command. I tried a 3rd time, but instead used the suggestion below to do <code>gem install rubygems-update &amp;&amp; update_rubygems</code>--that just resulted in a failed install, and kept me with a usable RubyGems 1.6.2.</p> <p>I'd like to a) use RubyGems 1.8.x, and b) undo these changes as opposed to having to blow away my 1.9.2 install <em>again</em>. Any ideas? I'm running:</p> <ul> <li>rvm 1.6.5</li> <li>MRI 1.9.2</li> </ul> <pre> RubyGems Environment: - RUBYGEMS VERSION: 1.6.2 - RUBY VERSION: 1.9.2 (2011-02-18 patchlevel 180) [x86_64-darwin10.7.0] - INSTALLATION DIRECTORY: /Users/sloveless/.rvm/gems/ruby-1.9.2-p180 - RUBY EXECUTABLE: /Users/sloveless/.rvm/rubies/ruby-1.9.2-p180/bin/ruby - EXECUTABLE DIRECTORY: /Users/sloveless/.rvm/gems/ruby-1.9.2-p180/bin - RUBYGEMS PLATFORMS: - ruby - x86_64-darwin-10 - GEM PATHS: - /Users/sloveless/.rvm/gems/ruby-1.9.2-p180 - /Users/sloveless/.rvm/gems/ruby-1.9.2-p180@global - GEM CONFIGURATION: - :update_sources => true - :verbose => true - :benchmark => false - :backtrace => false - :bulk_threshold => 1000 - :sources => ["http://rubygems.org"] - REMOTE SOURCES: - http://rubygems.org</pre> <p>FWIW, there was a similar bug logged in the RubyGems bug repo just today (May 10), and I added similar info to that, <a href="http://rubyforge.org/tracker/index.php?func=detail&amp;aid=29196&amp;group_id=126&amp;atid=575" rel="nofollow">here</a></p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USturboladen
    1. USturboladen
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POHow do I get `gem` working again after upgrading to rubygems 1.8.x?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POHow do I get `gem` working again after upgrading to rubygems 1.8.x?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POHow do I get `gem` working again after upgrading to rubygems 1.8.x?
      1. USBarry
      1. VTFavorite
    1. COWhat does `which gem` tell you?
      singulars
      1. POHow do I get `gem` working again after upgrading to rubygems 1.8.x?
      1. USthe Tin Man
    2. CO`/Users/sloveless/.rvm/rubies/ruby-1.9.2-p180/bin/gem`
      singulars
      1. POHow do I get `gem` working again after upgrading to rubygems 1.8.x?
      1. USturboladen
    3. COThank you so much for this - I had to re-install and ended up with a new version of rubygems, and everything was messed up. This helps!
      singulars
      1. POHow do I get `gem` working again after upgrading to rubygems 1.8.x?
      1. USJamie Penney
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload