Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Replace :rubygems in Gemfile with 'https://rubygems.org'. #183

Conversation

zekefast
Copy link
Contributor

Bundler some time ago started display warning message like follow:

The source :rubygems is deprecated because HTTP requests are insecure.
Please change your source to 'https://rubygems.org' if possible, or
'http://rubygems.org' if not.

So, this change is to remove it and let everything go smother.

Bundler some time ago started display warning message like follow:

The source :rubygems is deprecated because HTTP requests are insecure.
Please change your source to 'https://rubygems.org' if possible, or
'http://rubygems.org' if not.

So, this change is to remove it and let everything go smother.
grosser added a commit that referenced this pull request Feb 18, 2013
…re_source_in_gemfile

Replace :rubygems in Gemfile with 'https://rubygems.org'.
@grosser grosser merged commit 838373e into grosser:master Feb 18, 2013
@grosser
Copy link
Owner

grosser commented Feb 18, 2013

Thanks for the pull and wtf @bundler changing defaults is evil now I guess...

@zekefast
Copy link
Contributor Author

I thing that was made because of recent BIG problems with rubygems repo.

@dscott22099
Copy link

I am getting the same message, but, I am running under Windows 2008. Cannot locate a "genfile" anywhere on my system. Is there a different location or filename for this file under Windows 2008?

@grosser
Copy link
Owner

grosser commented Dec 31, 2013

it's Gemfile and you should change it in your projects Gemfile, not in parallel_tests

@dscott22099
Copy link

Thanks for help. Feel kind of stupid though, should have cut and pasted the word 'gemfile'. I am new to all of this, and am finding some of the error messages very cryptic sometimes.
When you say 'projects Gemfile', do you mean the Gemfile that is located in the this folder 'C:\BitNami\redmine-2.4.1-1\apps\redmine\htdocs'? If so, at the top of this file it already says 'source 'https://rubygems.org'. Here is the error or warning message I am getting..

C:\BitNami\redmine-2.4.1-1\apps\redmine\htdocs>bundle install --without development test postgresql sqlite
ment
The source :rubygems is deprecated because HTTP requests are insecure.
Please change your source to 'https://rubygems.org' if possible, or 'http://rubygems.org' if not.

I am not sure it is even an issue, but, I am finding that very few plugins seem to run as they should.

My actual experience with any of the parts of this is what I have managed to figure out. I find that most of the documentation I have found assumes the user already has working knowledge of Linux type systems. My experience is purely Windows based. Any help is greatly appreciated.
'

@dscott22099
Copy link

I just tried looking in the gemfiles located in the plugins I am using, found one that did not have source 'https://rubygems.org' in it. I changed that gemfile and ran the bundle command again, this time no error. Not sure if it is correct, but it did make a difference.

@zekefast
Copy link
Contributor Author

zekefast commented Jan 1, 2014

@dscott22099, changing plugins' code itself is a "dirty" way to fix it, because you lost your fixes as soon as you get update for the plugin. There is a better way submit you change to developer of the plugin and ask him to merge you fixes. Do not forget to provide reasonable description to you changes. ;) Sure it require you some knowledge of git or some other VCS depending on what error prone plugin is used.

@zekefast
Copy link
Contributor Author

zekefast commented Jan 1, 2014

Happy New Year, BTW! :D

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants