predicated gem error

32 views
Skip to first unread message

Joel VanderWerf

unread,
May 18, 2011, 5:37:38 PM5/18/11
to wron...@googlegroups.com

Hi, and congrats, predicated just busted rubygems, twice!:

$ sudo gem update
Updating installed gems
Updating predicated
Fetching: predicated-0.2.4.gem (100%)
Invalid gemspec in
[/usr/local/lib/ruby/gems/1.8/specifications/predicated-0.2.4.gemspec]:
invalid date format in specification: "2010-07-06 00:00:00.000000000Z"
ERROR: While executing gem ... (NoMethodError)
undefined method `name' for nil:NilClass

$ gem list
Invalid gemspec in
[/usr/local/lib/ruby/gems/1.8/specifications/predicated-0.2.4.gemspec]:
invalid date format in specification: "2010-07-06 00:00:00.000000000Z"
/usr/local/lib/ruby/site_ruby/1.8/rubygems/specification.rb:277:in
`_resort!': undefined method `name' for nil:NilClass (NoMethodError)
from /usr/local/lib/ruby/site_ruby/1.8/rubygems/specification.rb:276:in
`sort!'
from /usr/local/lib/ruby/site_ruby/1.8/rubygems/specification.rb:276:in
`_resort!'
from /usr/local/lib/ruby/site_ruby/1.8/rubygems/specification.rb:270:in
`_all'


I had to fix the date manually. Actually it seems like a bug in rubygems
that a bad date in one spec could bring the whole system down.

Alex Chaffee

unread,
May 18, 2011, 5:59:31 PM5/18/11
to wron...@googlegroups.com
The date spec thing is a rubygems bug. It seems to happen when the releaser (me) generates a gem with RubyGems 1.8.2, and only shows up on some people's systems when they install said gem (i.e. I didn't catch it cause it worked for me). I'll do a new one asap and let you know when it's pushed.

What was the second bug? Or was that just the same bug twice?

See also 

 - Alex

Joel VanderWerf

unread,
May 18, 2011, 6:16:54 PM5/18/11
to wron...@googlegroups.com

It was the same bug twice, with 0.2.3 and 0.2.4 a few minutes later.
Thanks!

> Alex Chaffee - al...@stinky.com <mailto:al...@stinky.com> -

Alex Chaffee

unread,
May 18, 2011, 6:46:11 PM5/18/11
to wron...@googlegroups.com
OK, please try gem update again -- 0.2.6 might be money. (I'm releasing 3 different gems right now so I may have gotten a bit confused; if so, let me know and I'll try again.)

BTW the issue is actually with Ruby itself -- building the gem with 1.9.2p180 makes a metadata field with a different date format than building the gem with 1.9.2p0. And that new format is unreadable by older versions of Ruby. I think it's that they added fractional seconds to the time, and the poor old date parser breaks when it hits ".0000000".

 - A

Joel VanderWerf

unread,
May 18, 2011, 7:15:44 PM5/18/11
to wron...@googlegroups.com

All good now.

> <mailto:joelvan...@gmail.com

> <mailto:al...@stinky.com <mailto:al...@stinky.com>> -

Reply all
Reply to author
Forward
0 new messages