You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 3, 2023. It is now read-only.
I first installed ruby 2.0.0-p0 and installed gems. Then 2.0.0-195 was released, I installed it and eventually removed 2.0.0-p0. All that with the communal gems plugin.
Since the bundle command didn't work anymore, I noticed that (almost) all bin files located in ~/.rbenv/gems/2.0.0/bin have a shebang pointing to a ruby binary, like #!/home/julien/.rbenv/versions/2.0.0-p0/bin/ruby, instead of the generic #! /usr/bin/env ruby.
I suppose that shouldn't happen?
The text was updated successfully, but these errors were encountered:
I first installed ruby 2.0.0-p0 and installed gems. Then 2.0.0-195 was released, I installed it and eventually removed 2.0.0-p0. All that with the communal gems plugin.
Since the bundle command didn't work anymore, I noticed that (almost) all bin files located in
~/.rbenv/gems/2.0.0/bin
have a shebang pointing to a ruby binary, like#!/home/julien/.rbenv/versions/2.0.0-p0/bin/ruby
, instead of the generic#! /usr/bin/env ruby
.I suppose that shouldn't happen?
The text was updated successfully, but these errors were encountered: