<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: &#8220;version_requirements deprecated&#8221; warning in rails</title>
	<atom:link href="http://www.mattvsworld.com/blog/2010/03/version_requirements-deprecated-warning-in-rails/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mattvsworld.com/blog/2010/03/version_requirements-deprecated-warning-in-rails/#utm_source=feed&amp;utm_medium=feed&amp;utm_campaign=feed</link>
	<description>bring it on, world!</description>
	<lastBuildDate>Tue, 07 Sep 2010 05:05:45 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Anurag</title>
		<link>http://www.mattvsworld.com/blog/2010/03/version_requirements-deprecated-warning-in-rails/comment-page-1/#comment-505</link>
		<dc:creator>Anurag</dc:creator>
		<pubDate>Fri, 25 Jun 2010 11:23:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.mattvsworld.com/blog/?p=470#comment-505</guid>
		<description>@Dan, &quot;sudo ls&quot; - shorter way to let sudo remember you</description>
		<content:encoded><![CDATA[<p>@Dan, &#8220;sudo ls&#8221; &#8211; shorter way to let sudo remember you</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan Tripp</title>
		<link>http://www.mattvsworld.com/blog/2010/03/version_requirements-deprecated-warning-in-rails/comment-page-1/#comment-301</link>
		<dc:creator>Dan Tripp</dc:creator>
		<pubDate>Wed, 12 May 2010 03:59:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.mattvsworld.com/blog/?p=470#comment-301</guid>
		<description>THANK YOU!  :)

I used Lou&#039;s tip, with the added step of doing &quot;sudo ping yahoo.com&quot; first so that I could enter the sudo password... otherwise it sorta &quot;hangs&quot; (in the bad way).</description>
		<content:encoded><![CDATA[<p>THANK YOU!  <img src='http://www.mattvsworld.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>I used Lou&#8217;s tip, with the added step of doing &#8220;sudo ping yahoo.com&#8221; first so that I could enter the sudo password&#8230; otherwise it sorta &#8220;hangs&#8221; (in the bad way).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anooj Rajan</title>
		<link>http://www.mattvsworld.com/blog/2010/03/version_requirements-deprecated-warning-in-rails/comment-page-1/#comment-209</link>
		<dc:creator>Anooj Rajan</dc:creator>
		<pubDate>Wed, 21 Apr 2010 20:23:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.mattvsworld.com/blog/?p=470#comment-209</guid>
		<description>Thanks for the patch.. Worked like a charm...</description>
		<content:encoded><![CDATA[<p>Thanks for the patch.. Worked like a charm&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Christopher Dwan</title>
		<link>http://www.mattvsworld.com/blog/2010/03/version_requirements-deprecated-warning-in-rails/comment-page-1/#comment-99</link>
		<dc:creator>Christopher Dwan</dc:creator>
		<pubDate>Thu, 25 Mar 2010 19:22:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.mattvsworld.com/blog/?p=470#comment-99</guid>
		<description>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&#039;t have. I skipped patching that file and it appears to have worked fine.</description>
		<content:encoded><![CDATA[<p>Yes. I just ignored this error for a few weeks and finally went looking for an answer and POOF! Gone.</p>
<p>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&#8217;t have. I skipped patching that file and it appears to have worked fine.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: matt</title>
		<link>http://www.mattvsworld.com/blog/2010/03/version_requirements-deprecated-warning-in-rails/comment-page-1/#comment-90</link>
		<dc:creator>matt</dc:creator>
		<pubDate>Tue, 23 Mar 2010 17:12:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.mattvsworld.com/blog/?p=470#comment-90</guid>
		<description>good tip, thanks! --

You are right that patching system gems isn&#039;t the safest thing in the world to do -- an update might overwrite what you&#039;ve done, or you could accidentally break something you don&#039;t mean to.  In this case, it&#039;s a rather trivial alteration, that shouldn&#039;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...</description>
		<content:encoded><![CDATA[<p>good tip, thanks! &#8211;</p>
<p>You are right that patching system gems isn&#8217;t the safest thing in the world to do &#8212; an update might overwrite what you&#8217;ve done, or you could accidentally break something you don&#8217;t mean to.  In this case, it&#8217;s a rather trivial alteration, that shouldn&#8217;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&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lou</title>
		<link>http://www.mattvsworld.com/blog/2010/03/version_requirements-deprecated-warning-in-rails/comment-page-1/#comment-89</link>
		<dc:creator>Lou</dc:creator>
		<pubDate>Tue, 23 Mar 2010 16:51:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.mattvsworld.com/blog/?p=470#comment-89</guid>
		<description>I didn&#039;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 &#124; 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&#039;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 &#124; sudo patch -d /Library/Ruby/Gems/1.8/gems/rails-2.3.5/lib/rails -R</description>
		<content:encoded><![CDATA[<p>I didn&#8217;t know how to apply the committed patch, so in case others have the same problem: </p>
<p>curl <a href="http://github.com/rails/rails/commit/268c9040d5c3c7ed30f3923eee71a78eeece8a8a.diff" rel="nofollow">http://github.com/rails/rails/commit/268c9040d5c3c7ed30f3923eee71a78eeece8a8a.diff</a> | sudo patch -d /Library/Ruby/Gems/1.8/gems/rails-2.3.5/lib/rails</p>
<p>Just remember to switch out the directory after -d with wherever gem_dependency.rb lives on your system (it&#8217;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 <img src='http://www.mattvsworld.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>Oh, and if something goes wrong, reverse the patch with: </p>
<p>curl <a href="http://github.com/rails/rails/commit/268c9040d5c3c7ed30f3923eee71a78eeece8a8a.diff" rel="nofollow">http://github.com/rails/rails/commit/268c9040d5c3c7ed30f3923eee71a78eeece8a8a.diff</a> | sudo patch -d /Library/Ruby/Gems/1.8/gems/rails-2.3.5/lib/rails -R</p>
]]></content:encoded>
	</item>
</channel>
</rss>
