Comments on: “version_requirements deprecated” warning in rails

By: mltsy

mltsy — Fri, 25 Feb 2011 17:14:56 +0000

I was getting nearly this same error, only it was in bundler, and said:

Warning: Gem::LoadError#version_requirement= is deprecated and will be removed on or after January 2011. Use #requirement.

I found that updating to bundler 1.0.10 fixed it.

By: Fireproof Socks

Fireproof Socks — Wed, 02 Feb 2011 21:06:54 +0000

Just pointing out that the URL to the GIT patch has changed, so you have to change it to run Lou’s command. It should use HTTPS:
https://github.com/rails/rails/commit/268c9040d5c3c7ed30f3923eee71a78eeece8a8a.diff

You can also use “sudo -i” to give you interactive sudo access, which looks pretty much the same way as if you had done “su – root”

By: Anurag

Anurag — Fri, 25 Jun 2010 11:23:55 +0000

@Dan, “sudo ls” – shorter way to let sudo remember you

By: Dan Tripp

Dan Tripp — Wed, 12 May 2010 03:59:09 +0000

THANK YOU!

I used Lou’s tip, with the added step of doing “sudo ping yahoo.com” first so that I could enter the sudo password… otherwise it sorta “hangs” (in the bad way).

By: Anooj Rajan

Anooj Rajan — Wed, 21 Apr 2010 20:23:31 +0000

Thanks for the patch.. Worked like a charm…

By: Christopher Dwan

Christopher Dwan — Thu, 25 Mar 2010 19:22:56 +0000

Yes. I just ignored this error for a few weeks and finally went looking for an answer and POOF! Gone.

That command from Lou worked for me just cut and paste to the command line. The only thing was that the patch was looking for gem_dependency_test.rb which my system apparently doesn’t have. I skipped patching that file and it appears to have worked fine.

By: matt

matt — Tue, 23 Mar 2010 17:12:54 +0000

good tip, thanks! –

You are right that patching system gems isn’t the safest thing in the world to do — an update might overwrite what you’ve done, or you could accidentally break something you don’t mean to. In this case, it’s a rather trivial alteration, that shouldn’t have any nasty side affects. A safer alternative may be to localize your rails gem in your /vendor directory, and apply the patch there. That way you leave your system rails untouched…

By: Lou

Lou — Tue, 23 Mar 2010 16:51:59 +0000

I didn’t know how to apply the committed patch, so in case others have the same problem:

curl http://github.com/rails/rails/commit/268c9040d5c3c7ed30f3923eee71a78eeece8a8a.diff | sudo patch -d /Library/Ruby/Gems/1.8/gems/rails-2.3.5/lib/rails

Just remember to switch out the directory after -d with wherever gem_dependency.rb lives on your system (it’s in the warning message). It is probably bad practice to patch your system gems, but to get rid of this warning we can make an exception

Oh, and if something goes wrong, reverse the patch with:

curl http://github.com/rails/rails/commit/268c9040d5c3c7ed30f3923eee71a78eeece8a8a.diff | sudo patch -d /Library/Ruby/Gems/1.8/gems/rails-2.3.5/lib/rails -R