Bug #5960

Error with rvm default gemset and rails rake

Added by Yura Sokolov almost 4 years ago. Updated almost 4 years ago.

Status:Third Party's Issue
ruby -v:ruby 1.9.3p0 (2011-10-30 revision 33570) [i686-linux] Backport:


After installing fresh ruby, creating fresh rails application, rake db:migrate fails with evident bug in requiring files
(already created constants, files are required from ~/.rvm/gems/ruby-1.9.3-p0@global/gems/rake- and from ~/.rvm/gems/ruby-1.9.3-p0/gems/rake-

Error disappeared when not default gemset is used.



#1 Updated by Yura Sokolov almost 4 years ago

I could not really say, if this bug of Ruby or RVM

#2 Updated by Yui NARUSE almost 4 years ago

  • Status changed from Open to Third Party's Issue

It is because,
* the command rake is /home/yura/.rvm/gems/ruby-1.9.3-p0-test/bin/rake.
so it loads files in /home/yura/.rvm/gems/ruby-1.9.3-p0-test@global/gems/rake-
* but on the line 'gem "rake"' it loads files in /home/yura/.rvm/gems/ruby-1.9.3-p0-test@global/gems/rake-
maybe because of its LOADPATH.
So they are conflicted.

This seems rvm's bug; PATH environment variable and LOADPATH should be consistent.

Also available in: Atom PDF