Hi all
I'm getting a massive amount of gemspec warnings to STDERR in Ruby 1.9.1
whenever 'rubygems/specification' gets required. The error I'm seeing is:
WARNING: #<NoMethodError: undefined method `>' for nil:NilClass>
WARNING: Invalid .gemspec format in
'/Users/rsanheim/.gem/ruby/1.9.1/specifications/rake-0.8.7.gemspec'
This is happening for just about any gem I install under 1.9, so I don't
think its an issue specific to any one gem. I *only* see the warnings if I
require rubygems/specification -- I can use gems and require rubygems
without the issue.
I've included full output of the issue on pastie, because the log is pretty
long, as gems spits out the full gemspec along side the warnings:
Hey... Did you get a fix for this?
I'm also seeing the same issue. Snow Leopard, ruby 1.9.1
It is definitely a problem with the 'jeweler' gem. I'm raising a bug
in github now...
···
On Sep 7, 6:02 pm, Rob Sanheim <rsanh...@gmail.com> wrote:
Hi all
I'm getting a massive amount of gemspec warnings to STDERR in Ruby 1.9.1
whenever 'rubygems/specification' gets required. The error I'm seeing is:
WARNING: #<NoMethodError: undefined method `>' for nil:NilClass>
WARNING: Invalid .gemspec format in
'/Users/rsanheim/.gem/ruby/1.9.1/specifications/rake-0.8.7.gemspec'
This is happening for just about any gem I install under 1.9, so I don't
think its an issue specific to any one gem. I *only* see the warnings if I
require rubygems/specification -- I can use gems and require rubygems
without the issue.
I've included full output of the issue on pastie, because the log is pretty
long, as gems spits out the full gemspec along side the warnings:
On Sep 7, 6:02 pm, Rob Sanheim <rsanh...@gmail.com> wrote:
> Hi all
> I'm getting a massive amount of gemspec warnings to STDERR in Ruby 1.9.1
> whenever 'rubygems/specification' gets required. The error I'm seeing
is:
>
> WARNING: #<NoMethodError: undefined method `>' for nil:NilClass>
> WARNING: Invalid .gemspec format in
> '/Users/rsanheim/.gem/ruby/1.9.1/specifications/rake-0.8.7.gemspec'
>
> This is happening for just about any gem I install under 1.9, so I don't
> think its an issue specific to any one gem. I *only* see the warnings if
I
> require rubygems/specification -- I can use gems and require rubygems
> without the issue.
>
> I've included full output of the issue on pastie, because the log is
pretty
> long, as gems spits out the full gemspec along side the warnings:
>
> http://pastie.org/608299
>
> Note that the log is from Leopard, but I've also seen the issue on Ubuntu
> 8.10.
>
> Does this look like something I'm installing wrong, or should I file an
> issue against rubygems?
>
> Thanks,
> Rob
I have rubygems installed because the first thing I do after installing Ruby
1.9 is to run gem update --system, which updates gems to 1.3.5. I had
forgotten that that just turns around and installs rubygems-update - so I
actually did use rubygems-update.
So, this is a problem for anyone who wants ruby 1.9 plus gems 1.3.5.
Reverting to gems 1.3.1 "fixes" it:
$ rm -r
/Users/rsanheim/.rvm/ruby-1.9.1-p243/lib/ruby/site_ruby/1.9.1/rubygem*
$ gem -v
1.3.1
$ ruby -rubygems -rrubygems/specification -e 'gem "hoe"; require "hoe"; puts
"hi"'
hi
$ gem update --system
Updating RubyGems
Updating rubygems-update
Successfully installed rubygems-update-1.3.5
Updating RubyGems to 1.3.5
Installing RubyGems 1.3.5
RubyGems 1.3.5 installed
$ gem -v
1.3.5
$ ruby -rubygems -rrubygems/specification -e 'gem "hoe"; require "hoe"; puts
"hi"'
WARNING: #<NoMethodError: undefined method `>' for nil:NilClass>
# -*- encoding: utf-8 -*-
# .....
# same error, produces error log of every gemspec installed
Besides, I've seen this on other developer's machines, so its clearly not a
'just on my box' bug.
- Rob
···
On Thu, Sep 10, 2009 at 6:18 PM, Ryan Davis <ryand-ruby@zenspider.com>wrote:
On Sep 10, 2009, at 14:36 , Rob Sanheim wrote:
On Thu, Sep 10, 2009 at 4:57 PM, Ryan Davis <ryand-ruby@zenspider.com >> >wrote:
On Sep 10, 2009, at 13:50 , Ryan Davis wrote:
On Sep 10, 2009, at 13:42 , Rob Sanheim wrote:
I don't think so, I can reproduce this without jeweler in the mix at
all.
/Users/rsanheim/.rvm/ruby-1.9.1-p243/lib/ruby/site_ruby/1.9.1/rubygems.rb:827:in
`report_activate_error': Could not find RubyGem hoe (>= 0)
(Gem::LoadError)
from
/Users/rsanheim/.rvm/ruby-1.9.1-p243/lib/ruby/site_ruby/1.9.1/rubygems.rb:261:in
`activate'
from
/Users/rsanheim/.rvm/ruby-1.9.1-p243/lib/ruby/site_ruby/1.9.1/rubygems.rb:68:in
`gem'
from -e:1:in `<main>'
Why do you have rubygems installed on 1.9.1? I think that's the entire
problem.
I have rubygems installed because the first thing I do after installing Ruby
1.9 is to run gem update --system, which updates gems to 1.3.5. I had
forgotten that that just turns around and installs rubygems-update - so I
actually did use rubygems-update.
Well, I recommend you don't do that.
Reverting to gems 1.3.1 "fixes" it:
It doesn't "fix" it, it fixes it.
Besides, I've seen this on other developer's machines, so its clearly not a
'just on my box' bug.
Nobody implied that it was. It will happen on any instance of 1.9 where you install your own rubygems update. So, for now, don't do that.
Am I missing something? how do you update rubygems with 1.9? Is there
a new process?
Thanks
···
On Sep 10, 8:06 pm, Ryan Davis <ryand-r...@zenspider.com> wrote:
On Sep 10, 2009, at 18:56 , Rob Sanheim wrote:
> I have rubygems installed because the first thing I do after
> installing Ruby
> 1.9 is to run gem update --system, which updates gems to 1.3.5. I
> had
> forgotten that that just turns around and installs rubygems-update -
> so I
> actually did use rubygems-update.
Well, I recommend you don't do that.
> Reverting to gems 1.3.1 "fixes" it:
It doesn't "fix" it, it fixes it.
> Besides, I've seen this on other developer's machines, so its
> clearly not a
> 'just on my box' bug.
Nobody implied that it was. It will happen on any instance of 1.9
where you install your own rubygems update. So, for now, don't do that.
Rubygems comes bundled with Ruby 1.9, but IIRC its version 1.3.1 - or at
least it reports itself as such. So once you run gem update --system, the
bug appears, at least until you remove that gem update.
- Rob
···
On Wed, Sep 23, 2009 at 10:18 PM, Andreas Haller <andreashaller@gmail.com>wrote:
Don French wrote:
> On Sep 10, 8:06�pm, Ryan Davis <ryand-r...@zenspider.com> wrote:
>> Well, I recommend you don't do that.
>> where you install your own rubygems update. So, for now, don't do that.
> Am I missing something? how do you update rubygems with 1.9? Is there
> a new process?
> Thanks
Don, i think you just don't. Rubygems now is part of/comes bunded with
Ruby 1.9.
However, i was having the same issue runnig on ruby 1.9.2dev (2009-09-15
trunk 24928) [-darwin9.8.0], but only with a library/gem using Jeweler.