search

rubygems / rubygems-test

An attempt to replace the testing facility in rubygems via a test plugin.
Other
47 stars 11 forks source link

Gem::RakeNotFoundError installing tzinfo with Bundler #11

Closed capoferro closed 13 years ago

capoferro commented 13 years ago

Installing tzinfo (0.3.24) /home/josiah/.rvm/gems/ruby-1.9.2-p0/gems/rubygems-test-0.2.5/lib/rubygems/on_install_test.rb:13:in rescue in block in <top (required)>': uninitialized constant Gem::RakeNotFoundError (NameError) from /home/josiah/.rvm/gems/ruby-1.9.2-p0/gems/rubygems-test-0.2.5/lib/rubygems/on_install_test.rb:11:inblock in <top (required)>' from /home/josiah/.rvm/rubies/ruby-1.9.2-p0/lib/ruby/1.9.1/rubygems/installer.rb:216:in call' from /home/josiah/.rvm/rubies/ruby-1.9.2-p0/lib/ruby/1.9.1/rubygems/installer.rb:216:inblock in install' from /home/josiah/.rvm/rubies/ruby-1.9.2-p0/lib/ruby/1.9.1/rubygems/installer.rb:215:in each' from /home/josiah/.rvm/rubies/ruby-1.9.2-p0/lib/ruby/1.9.1/rubygems/installer.rb:215:ininstall' from /home/josiah/.rvm/gems/ruby-1.9.2-p0/gems/bundler-1.0.7/lib/bundler/source.rb:95:in install' from /home/josiah/.rvm/gems/ruby-1.9.2-p0/gems/bundler-1.0.7/lib/bundler/installer.rb:55:inblock in run' from /home/josiah/.rvm/gems/ruby-1.9.2-p0/gems/bundler-1.0.7/lib/bundler/spec_set.rb:12:in block in each' from /home/josiah/.rvm/gems/ruby-1.9.2-p0/gems/bundler-1.0.7/lib/bundler/spec_set.rb:12:ineach' from /home/josiah/.rvm/gems/ruby-1.9.2-p0/gems/bundler-1.0.7/lib/bundler/spec_set.rb:12:in each' from /home/josiah/.rvm/gems/ruby-1.9.2-p0/gems/bundler-1.0.7/lib/bundler/installer.rb:44:inrun' from /home/josiah/.rvm/gems/ruby-1.9.2-p0/gems/bundler-1.0.7/lib/bundler/installer.rb:8:in install' from /home/josiah/.rvm/gems/ruby-1.9.2-p0/gems/bundler-1.0.7/lib/bundler/cli.rb:225:ininstall' from /home/

erikh commented 13 years ago

Curious, do you get this when you install gems without bundler?

erikh commented 13 years ago

Can you test with the latest HEAD? I think I fixed this.

erikh commented 13 years ago

Gonna close this, I think it was fixed in 0.3.0