New errors re: Gem::Specification

Path	csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!aioe.org!news.stack.nl!talisker.lacave.net!lacave.net!not-for-mail
From	Forrest Aldrich <forrie@gmail.com>
Newsgroups	comp.lang.ruby
Subject	New errors re: Gem::Specification
Date	Thu, 19 May 2011 15:10:06 -0500
Organization	Service de news de lacave.net
Lines	11
Message-ID	<e954a4317c24af137b72650e5f3c1c4c@ruby-forum.com> (permalink)
NNTP-Posting-Host	bristol.highgroove.com
Content-Type	text/plain; charset=UTF-8
Content-Transfer-Encoding	7bit
X-Trace	talisker.lacave.net 1305835834 56630 65.111.164.187 (19 May 2011 20:10:34 GMT)
X-Complaints-To	abuse@lacave.net
NNTP-Posting-Date	Thu, 19 May 2011 20:10:34 +0000 (UTC)
X-Received-From	This message has been automatically forwarded from the ruby-talk mailing list by a gateway at comp.lang.ruby. If it is SPAM, it did not originate at comp.lang.ruby. Please report the original sender, and not us. Thanks! For more details about this gateway, please visit: http://blog.grayproductions.net/categories/the_gateway
X-Mail-Count	383490
X-Ml-Name	ruby-talk
X-Rubymirror	Yes
X-Ruby-Talk	<e954a4317c24af137b72650e5f3c1c4c@ruby-forum.com>
Xref	x330-a1.tempe.blueboxinc.net comp.lang.ruby:4783

Show key headers only | View raw

I read about Gem::Specification being deprecated soon; however, the
copious errors that I'm getting (from the many gems I use) is fast
becoming a pain in the a**.   With that said, is there a way I can
temporarily silence this warning?


thanks.... :-)

-- 
Posted via http://www.ruby-forum.com/.

Back to comp.lang.ruby | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

New errors re: Gem::Specification Forrest Aldrich <forrie@gmail.com> - 2011-05-19 15:10 -0500
  Re: New errors re: Gem::Specification Ryan Davis <ryand-ruby@zenspider.com> - 2011-05-19 15:39 -0500
    Re: New errors re: Gem::Specification Robert Dober <robert.dober@gmail.com> - 2011-05-20 09:06 -0500

csiph-web