"No version set for command bundle" when trying to add Ruby 2.5.5 to my toolchest

[cobbr2]

I've tried this several times, so my guess is that there's something I'm just doing wrong, but: I install ruby-2.5.5, update my .tool-versions. ruby --version finds the right Ruby. But bundle can't be found. Reshim doesn't work. Ubuntu 18.04, asdf version 0.7.3:

rcobb@rcobb-t480:~/warehouse$ bundle --version
asdf: No version set for command bundle
you might want to add one of the following in your .tool-versions file:

ruby ruby-2.5.1
ruby 2.5.3
ruby 2.6.2
ruby 2.5.1
ruby 2.3.8
ruby ruby-2.3.8
ruby 2.3.4
rcobb@rcobb-t480:~/warehouse$ asdf uninstall ruby 2.5.5 && asdf install ruby 2.5.5
Downloading ruby-build...
...
Installing ruby-2.5.5...
Installed ruby-2.5.5 to /home/rcobb/.asdf/installs/ruby/2.5.5


rcobb@rcobb-t480:~/warehouse$ bundle --version
asdf: No version set for command bundle
you might want to add one of the following in your .tool-versions file:

ruby ruby-2.5.1
ruby 2.5.3
ruby 2.6.2
ruby 2.5.1
ruby 2.3.8
ruby ruby-2.3.8
ruby 2.3.4

rcobb@rcobb-t480:~/warehouse$ asdf reshim
rcobb@rcobb-t480:~/warehouse$ bundle --version
asdf: No version set for command bundle
you might want to add one of the following in your .tool-versions file:

ruby ruby-2.5.1
ruby 2.5.3
ruby 2.6.2
ruby 2.5.1
ruby 2.3.8
ruby ruby-2.3.8
ruby 2.3.4
rcobb@rcobb-t480:~/warehouse$ ruby --version
ruby 2.5.5p157 (2019-03-15 revision 67260) [x86_64-linux]
rcobb@rcobb-t480:~/warehouse$ asdf list ruby
  2.1.5
  2.3.4
  2.3.8
  2.5.1
  2.5.3
  2.5.5
  2.6.2
  ruby-2.3.8
rcobb@rcobb-t480:~/warehouse$ asdf --version
v0.7.3

Am I doing something wrong? Thanks!

[cobbr2]

Yes. I'm failing to install bundler!

[betogrun]

I'm still facing this same error.
@cobbr2 did you manage to solve it?

[cobbr2]

I did... But I don't remember the answer today.

…

On Fri, Sep 27, 2019, 10:47 AM Alberto Rocha ***@***.***> wrote: I'm still facing this same error. @cobbr2 <https://github.com/cobbr2> did you manage to solve it? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#127?email_source=notifications&email_token=AAB43VPR7Y3UKBYAXV5FJD3QLZBLVA5CNFSM4IFJDY52YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7ZUDTQ#issuecomment-536035790>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAB43VPRXONE6MCFY2ZFDO3QLZBLVANCNFSM4IFJDY5Q> .

[betogrun]

No problems. @cobbr2 can you please reopen this issue?

[Stratus3D]

My guess is that you haven't yet installed bundler. We are aware that the error message is confusion and have an issue somewhere for this. The error should really say that there is no bundle executable, because there isn't one for the current version.

[betogrun]

You are right @Stratus3D.
Running gem install bundler solves the issue.
Thanks!

[ttilberg]

@Stratus3D Can you please review asdf-vm/asdf#557 (comment) with that same mindset? I get something similar, but am trying to explicitly install things to the correct version. Do you feel this is the same, or a different bug? Any insight?

[Stratus3D]

Hi @ttilberg, I read your other comment, good description of the issue. You are right about that line being a magic comment in the shim. The shim was generated at a time in the past when only Python 3.6.8 offered the ipython executable on your system. Now you have Python 3.7.4 installed and the shim file hasn't been updated to reflect that. Typically asdf reshim will update your shims. Can you try that and see if it has any affect on the contents of your ipython shim file?

[ttilberg]

Thank you @Stratus3D. That fixed it. Sorry for turning this into a customer support thread.

[Stratus3D]

No worries @ttilberg

[kaka-ruto]

gem install bundler didn't work for me.

But gem update --system did.

[Dwiga]

gem install bundler didn't work for me.

But gem update --system did.

thanks dude, it works on me

[doshinwills-okta]

$ asdf global ruby <RUBY_VERSION>

Solved the issue for me

[WaismanDourado]

Thanks @doshinwills-okta asdf global ruby <RUBY_VERSION> works for me!

[roberttravispierce]

For those still having this issue in a Rails project, try prefacing the rails command with bundle exec... (e.g. bundle exec rails server)