This repository has been archived by the owner on Apr 14, 2021. It is now read-only.
1.3.0 switches meaning of source :rubygems to https? #2345
Comments
Http is deprecated but still supported. To avoid this warning message just switch to |
Just saying, Gemfiles w/ |
Cannot reproduce it with |
Yes, this only affects jruby-1.6.x - jruby-1.7.x can do https w/out jruby-openssl gem, apparently. |
Not a terrible issue - trivial workaround is to change ":rubygems" to "http://rubygems.org", or just "gem install jruby-openssl" (or even upgrade to jruby 1.7) - just giving a heads-up of the change. |
Seems to fix it - thanks! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Same Gemfile we've always been using, w/
source :rubygems
.Been getting that deprecation warning on that for like a week or two now.
This morning things started breaking on jruby-1.6.7
https://gist.github.com/LeifWarner/5042799
A coworker fixed it by changing
:rubygems
tohttp://rubygems.org/
.I fixed it by doing a
gem install jruby-openssl
beforehand.Curious that deprecation message still says:
"The source :rubygems is deprecated because HTTP requests are insecure."
and then further down it says:
"Fetching gem metadata from http://rubygems.org/"
after installing jruby-openssl, and still leaving the source as
:rubygems
.The text was updated successfully, but these errors were encountered: