Borken RVM, the installation dir is hardcoded "mpais" #1172

Closed
chengguangnan opened this Issue Oct 1, 2012 · 9 comments

Comments

Projects
None yet
5 participants
@chengguangnan

I'm doing a new RVM install.

Then I found that I can install any gems because /Users/mpais is not accessible.

@mpapis

rvm 1.16.6 (stable) by Wayne E. Seguin <wayneeseguin@gmail.com>, Michal Papis <mpapis@gmail.com> [https://rvm.io/]
 $ gem env
RubyGems Environment:
  - RUBYGEMS VERSION: 1.8.24
  - RUBY VERSION: 1.9.3 (2012-04-20 patchlevel 194) [x86_64-darwin12.2.0]
  - INSTALLATION DIRECTORY: /Users/mpapis/.rvm/gems/ruby-1.9.3-p194
  - RUBY EXECUTABLE: /Users/guangnan/.rvm/rubies/ruby-1.9.3-p194/bin/ruby
  - EXECUTABLE DIRECTORY: /Users/mpapis/.rvm/gems/ruby-1.9.3-p194/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86_64-darwin-12
  - GEM PATHS:
     - /Users/mpapis/.rvm/gems/ruby-1.9.3-p194
     - /Users/guangnan/.rvm/gems/ruby-1.9.3-p194
     - /Users/guangnan/.rvm/gems/ruby-1.9.3-p194@global
@richo

This comment has been minimized.

Show comment Hide comment
@richo

richo Oct 1, 2012

Member

I believe this is fixed in HEAD.

Can you rvm get head ?

Member

richo commented Oct 1, 2012

I believe this is fixed in HEAD.

Can you rvm get head ?

@chengguangnan

This comment has been minimized.

Show comment Hide comment
@chengguangnan

chengguangnan Oct 1, 2012

Not fully fixed as I can tell. I tested rvm get head and it has the correct directories the first time you gem env. But on a new shell env or something, it goes back to mpapis.

I tried rvm 1.16.5, same problem. I have rm -rf ~/.rvm between installs.

I checked '1.15.10' which works.

Not fully fixed as I can tell. I tested rvm get head and it has the correct directories the first time you gem env. But on a new shell env or something, it goes back to mpapis.

I tried rvm 1.16.5, same problem. I have rm -rf ~/.rvm between installs.

I checked '1.15.10' which works.

@richo

This comment has been minimized.

Show comment Hide comment
@richo

richo Oct 1, 2012

Member

I just did git grep mpapis on current master , and none of the hits were in executable codepaths.

When you say new shell env, can you elaborate?

Member

richo commented Oct 1, 2012

I just did git grep mpapis on current master , and none of the hits were in executable codepaths.

When you say new shell env, can you elaborate?

@bknowles

This comment has been minimized.

Show comment Hide comment
@bknowles

bknowles Oct 2, 2012

We're seeing what appears to be the same problem, also referenced in wayneeseguin#1157. We'll try the solution from @rkbodenner and report back.

bknowles commented Oct 2, 2012

We're seeing what appears to be the same problem, also referenced in wayneeseguin#1157. We'll try the solution from @rkbodenner and report back.

@mpapis

This comment has been minimized.

Show comment Hide comment
@mpapis

mpapis Oct 2, 2012

Member

this paths are coming most likely from the binary ruby, this is different issue then in #1157, this looks more like a duplicate of #1146

Member

mpapis commented Oct 2, 2012

this paths are coming most likely from the binary ruby, this is different issue then in #1157, this looks more like a duplicate of #1146

@ghost ghost assigned mpapis Oct 3, 2012

@mpapis

This comment has been minimized.

Show comment Hide comment
@mpapis

mpapis Oct 8, 2012

Member

code is fixed in 1.16.10 with 0f3af07

new binary rubies will come a bit later

Member

mpapis commented Oct 8, 2012

code is fixed in 1.16.10 with 0f3af07

new binary rubies will come a bit later

@mpapis

This comment has been minimized.

Show comment Hide comment
@mpapis

mpapis Oct 17, 2012

Member

RVM 1.16.14 contains new set of binary rubies, please try again:

rvm get stable
rvm reload
rvm reinstall 1.9.3
Member

mpapis commented Oct 17, 2012

RVM 1.16.14 contains new set of binary rubies, please try again:

rvm get stable
rvm reload
rvm reinstall 1.9.3
@mpapis

This comment has been minimized.

Show comment Hide comment
@mpapis

mpapis Oct 22, 2012

Member

I suppose it's fixed, let me know if there are still issues

Member

mpapis commented Oct 22, 2012

I suppose it's fixed, let me know if there are still issues

@mpapis mpapis closed this Oct 22, 2012

@ashchan

This comment has been minimized.

Show comment Hide comment
@ashchan

ashchan Oct 23, 2012

@mpapis Thanks just tried 1.16.16 and it works great!

ashchan commented Oct 23, 2012

@mpapis Thanks just tried 1.16.16 and it works great!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment