0

I'm trying to get up and running with ruby and the jekyll gem on my fresh instance of Ubuntu 16.04.

    usernamehere@usernamehere-hp:~/workspace/username.github.io$ ls -la /usr/local/bin/bundler
    -rwxr-xr-x 1 root root 498 Apr 18 18:18 /usr/local/bin/bundler
    usernamehere@usernamehere-hp:~/workspace/username.github.io$ ls -la /usr/local/bin/bundle
    -rwxr-xr-x 1 root root 497 Apr 18 18:18 /usr/local/bin/bundle
    usernamehere@usernamehere-hp:~/workspace/username.github.io$ ls -la /usr/bin/bundle
    -rwxr-xr-x 1 root root 590 Mar 13  2016 /usr/bin/bundle
    usernamehere@usernamehere-hp:~/workspace/username.github.io$ ls -la /usr/bin/bundler
    -rwxr-xr-x 1 root root 590 Mar 13  2016 /usr/bin/bundler

But I seem to have 2 or 4 copies of the ruby gem bundler installed. This is giving me conflicting things when I do things like:

bundle update vs sudo bundle update and bundle exec jekyll serve vs. sudo bundle exec jekyll serve

I'm also getting conflicting responses when I run bundle update vs bundler update vs sudo bundle update vs sudo bundler update.

What the heck is going on? I don't mind keeping only the ones in /usr/bin but I don't know if I should be using bundle or bundler or how to unsintall the entries in /usr/local/bin.

Any ideas?

1 Answers1

1

I think you used sudo apt install ruby to get ruby in your system. Which unfortunately is outdated and not the best way to use ruby.

Try completely purging your current ruby and re-installing it using either rvm or rbenv

You'll find a step by step guide here.

PS: You should never run bundler as ROOT, Completely removing all gems from system.

Sirajus Salekin
  • 1,737
  • 13
  • 29