https://bugs.ruby-lang.org/https://bugs.ruby-lang.org/favicon.ico?17113305112008-10-17T04:04:27ZRuby Issue Tracking SystemRuby master - Bug #653: `rake gem' emits a warninghttps://bugs.ruby-lang.org/issues/653?journal_id=13692008-10-17T04:04:27Zdrbrain (Eric Hodel)drbrain@segment7.net
<ul></ul><p>=begin<br>
On Oct 16, 2008, at 10:09 AM, Jim Weirich wrote:</p>
<blockquote>
<p>On Oct 16, 2008, at 11:47 AM, Yusuke ENDOH wrote:</p>
<blockquote>
<p>rake seems to call Gem.manage_gems which is deprecated at<br>
lib/rake/gempackagetask.rb.</p>
<p>$ sow19 foo<br>
(snip)<br>
$ cd fo/<br>
$ rake19<br>
(in /tmp/foo)<br>
<internal:0:Warning: Gem::manage_gems is deprecated and will be<br>
removed on or after March 2009.<br>
Hoe email value not set. aborting</p>
<p>Is it ok to merely remove the call?</p>
</blockquote>
<p>The gempackagetask should probably be allowed to continue to work<br>
with older gems. Can we put a version test around this?</p>
</blockquote>
<p>RubyGems back to 0.8.8 will work if Gem.manage_gems is replaced with:</p>
<p>require 'rubygems/builder'</p>
<p>since all manage_gems did was require extra files like this one.</p>
<p>As of today, these are the versions of RubyGems that accessed the<br>
repository recently:</p>
<p>$ cut -d ' ' -f 13 gemmirror-access_log | occur | grep RubyGems<br>
80668: "RubyGems/0.9.4"<br>
69239: "RubyGems/0.9.5<br>
22181: "RubyGems/0.9.2"<br>
12268: "RubyGems/1.0.1<br>
11679: "RubyGems/0.9.0"<br>
11155: "RubyGems/1.0.0<br>
8813: "RubyGems/0.9.4.6<br>
3153: "RubyGems/0.8.11"<br>
1040: "RubyGems/0.8.10"<br>
438: "RubyGems/0.9.3"<br>
417: "RubyGems/0.9.1"<br>
67: "RubyGems/0.9.4.7<br>
26: "RubyGems/0.9.4.3"<br>
25: "RubyGems/0.9.5"<br>
5: "RubyGems/0.8.8"<br>
3: "RubyGems/0.8.99.2"<br>
2: "RubyGems/0.9.4.4"<br>
2: "RubyGems/0.9.0.8"<br>
1: "RubyGems/0.9.4<br>
1: "RubyGems/0.9.4.5"</p>
<p>So I think you're fine to remove the Gem.manage_gems call.</p>
<p>=end</p> Ruby master - Bug #653: `rake gem' emits a warninghttps://bugs.ruby-lang.org/issues/653?journal_id=17932008-11-29T16:26:48Zko1 (Koichi Sasada)
<ul><li><strong>Assignee</strong> set to <i>drbrain (Eric Hodel)</i></li></ul><p>=begin</p>
<p>=end</p> Ruby master - Bug #653: `rake gem' emits a warninghttps://bugs.ruby-lang.org/issues/653?journal_id=19692008-12-11T12:12:20Zyugui (Yuki Sonoda)yugui@yugui.jp
<ul><li><strong>Priority</strong> changed from <i>3</i> to <i>5</i></li><li><strong>Target version</strong> set to <i>1.9.1 Release Candidate</i></li></ul><p>=begin</p>
<p>=end</p> Ruby master - Bug #653: `rake gem' emits a warninghttps://bugs.ruby-lang.org/issues/653?journal_id=19702008-12-11T12:13:00Zyugui (Yuki Sonoda)yugui@yugui.jp
<ul></ul><p>=begin<br>
Is this still reproduce? If not, close this issue.<br>
=end</p> Ruby master - Bug #653: `rake gem' emits a warninghttps://bugs.ruby-lang.org/issues/653?journal_id=20452008-12-14T00:46:21Zantares (Michael Klishin)
<ul></ul><p>=begin<br>
It has been removed in both trunk and 1_9_1, I think this should be closed now.<br>
=end</p> Ruby master - Bug #653: `rake gem' emits a warninghttps://bugs.ruby-lang.org/issues/653?journal_id=20522008-12-14T08:52:04Zzenspider (Ryan Davis)
<ul><li><strong>Status</strong> changed from <i>Open</i> to <i>Closed</i></li></ul><p>=begin</p>
<p>=end</p>