I am trying to do a bundle install which includes ruby-debug gem. However the installation fails with the error
linecache-0.43 has an invalid value for #cert_chain
I ma using rails 2.3.8, ruby 1.8.7 and RubyGems 1.7.1
Any help would be greatly appreciated.
Thanks!
solved this by downgrading my RubyGems from 1.7.1 to 1.6.2. Found it here
Rails 3 install error: "invalid value for #cert_chain"
Related
While attempting to solve another issue identified in this thread:
Error while trying to load the gem 'devise. ActiveSupport: Duration can't be coerced into Integer, I followed the suggested solution and changed my ruby version from 2.4.1 to 2.3.3 using rbenv. I also made similar changes in my Gemfile to reflect the new ruby version. However, when I tried to bundle install again, it throws an error saying that my ruby version is 2.4.1, when my Gem specified 2.3.3. However, running ruby -v shows my ruby version is on 2.3.3.
$ bundle install
Your Ruby version is 2.4.1, but your Gemfile specified 2.3.3
$ ruby -v
ruby 2.3.3p222 (2016-11-21 revision 56859) [x86_64-darwin16]
Any help here would be appreciated. Thank you!
Gem installation is specific to ruby version, so the bundler you're using is likely installed to your old ruby. Try installing bundler again:
gem install bundler
That should fix your problem.
I have a problem when running bundle install in the root of sharetribe rails's project. It shows me this error message:
Your Ruby version is 2.4.0, but your Gemfile specified 2.3.1
I tried installing rvm and installing the 2.3.1 version required to run this project but nothing changes and it still throwing this output.
Have anyone faced this problem before ?
Your Ruby version is 2.4.0, but your Gemfile specified 2.3.1
Steps to resolve this issue
1)rvm install ruby-2.3.1
2)gem install bundler
3)rvm use ruby-2.3.1
4)Bundle install
Your Ruby version is 2.4.0, but your Gemfile specified 2.3.1
If you run command ruby -v you can see that you have installed Ruby 2.4.0, when you look at the first line in your Gemfile specifies that you want to use Ruby 2.3.1.
You can do either install Ruby 2.3.1 or replace the first line in your Gemfile to with Ruby 2.4.0.
What does it say when you run bundle env in the terminal?
Is it the same ruby version?
I tried gem install bundler one time i had the same problem and bundle updated and worked.
You can read more about it here.
Good luck!
Im facing this problem when i'm installing bunder using command "bunlde install"
Initially i tried solving this issue by using following command
gem install autoprefixer-rails -v '6.2.2'
but again it said "autoprefixer-rails requires ruby version >= 2.0."
when i type
"ruby -v", my ruby version shows 2.3.0.
Next i have tried adding
ruby '2.3.0' to my gem file, then there was a conflict saying your ruby version is 1.9.3 but your gem file has 2.3.0
Need help how to proceed further.
Change your ruby version in the system first. If you using rvm then use following command.
rvm use 2.3.0
If you don't have it then install it by following command
rvm install 2.3.0
Delete the Gemfile.lock file and run
bundle install
Hopefully it will work. Thank you
Homebrew
My currently rails version is 4.1.6. I want to upgrade to 4.2.0beta2.But i had and error when i types this command
gem install rails 4.2.0beta2
i got this error.
ERROR: Could not find a valid gem '4.2.0beta2' (>= 0) in any repository
Anyones know how to fix it ? thanks!
You're missing a dot between the 0 and beta2.
gem install rails 4.2.0.beta2
First: You should use ruby RVM.
https://rvm.io/
Second: Take a look on this post:
Installing Rails 4.2.0.beta1 - Unresolved dependency found during sorting
I'm deploying to Ubuntu slice on slicehost, using Rails 2.1.0 (from gem)
If I try mongrel_rails start or script/server I get this error:
Rails requires RubyGems >= 0.9.4. Please install RubyGems
When I type gem -v I have version 1.2.0 installed. Any quick tips on what to look at to fix?
Have you tried reinstalling RubyGems? I had a pretty similar error message until I reuninstalled and for some reason, it installed into a different directory and then the problem went away.
Just finally found this answer... I was missing a gem, and thrown off by bad error message from Rails...