tag:help.rubygems.org,2010-01-19:/discussions/problems/583-spork-fails-to-work-with-rubygems-180181-but-works-with-172RubyGems.org: Discussion 2011-05-13T07:57:21Ztag:help.rubygems.org,2010-01-19:Comment/70329222011-05-06T11:48:14Z2011-05-06T11:48:15Zspork fails to work with rubygems 1.8.0/1.8.1 but works with 1.7.2<div><p>I'm seeing this too (rubygems 1.8.1, rvm ruby-1.9.2-p180)</p>
<p><code><br>
ahound(master|549m) $ spork<br>
NOTE: Gem::Specification#default_executable= is deprecated with no
replacement. It will be removed on or after 2011-10-01.<br>
Gem::Specification#default_executable= called from
/Users/mc/.rvm/gems/ruby-1.9.2-p180@global/specifications/bundler-1.0.0.rc.5.gemspec:10.<br>
NOTE: Gem::Specification#default_executable= is deprecated with no
replacement. It will be removed on or after 2011-10-01.<br>
Gem::Specification#default_executable= called from
/Users/mc/.rvm/gems/ruby-1.9.2-p180@global/specifications/rake-0.8.7.gemspec:10.<br>
NOTE: Gem.latest_load_paths is deprecated with no replacement. It
will be removed on or after 2011-10-01.<br>
Gem.latest_load_paths called from
/Users/mc/.rvm/gems/ruby-1.9.2-p180/gems/spork-0.9.0.rc5/lib/spork.rb:107.<br>
NOTE: Gem.all_partials is deprecated with no replacement. It will
be removed on or after 2011-10-01.<br>
Gem.all_partials called from
/Users/mc/.rvm/rubies/ruby-1.9.2-p180/lib/ruby/site_ruby/1.9.1/rubygems.rb:600.<br>
undefined method</code> basename' for
"/Users/mc/.rvm/gems/ruby-1.9.2-p180/gems/abstract-1.0.0":String
(NoMethodError)
/Users/mc/.rvm/rubies/ruby-1.9.2-p180/lib/ruby/site_ruby/1.9.1/rubygems.rb:601:inblock
in latest_partials'</p></div>Greg Btag:help.rubygems.org,2010-01-19:Comment/70329222011-05-07T18:34:08Z2011-05-07T18:34:09Zspork fails to work with rubygems 1.8.0/1.8.1 but works with 1.7.2<div><p>This is fixed in spork 0.9.0rc7.</p></div>Greg Btag:help.rubygems.org,2010-01-19:Comment/70329222011-05-13T07:57:19Z2011-05-13T07:57:19Zspork fails to work with rubygems 1.8.0/1.8.1 but works with 1.7.2<div><p>This was a bug on my part and not a matter of deprecation...
just a bug. It has been addressed in spork directly and the buggy
code will be fixed in the next revision of rubygems.</p>
<p>Sorry for the trouble.</p></div>Ryan Davis