I see this when I install (and when other gems depend on) json under rubygems 1.8.6:
Invalid gemspec in [/Users/ajsharp/.rvm/gems/ruby-1.9.2-p290@connie/specifications/json-1.6.1.gemspec]: invalid date format in specification: "2011-09-18 00:00:00.000000000Z"
Apparently you're not supposed to specify the date in the gemspec anymore. Sounds like an easy fix.
Fix #99. Date should no longer be specified in gemspec
Are you pushing a new version of the gem with this fix?
I'm having some issues with our windows installer and json's gemspec and I was wondering if I should go ahead, publish but point users to this entry and instructions on how to fix the .gemspec once the gem is installed or wait until you push a new version.
Can you give us a rough time-frame?
What's the story with this issue? When chef upgraded their json dependency from <= 1.5.2 to <= 1.6.1 this started blowing up for me. Is removing date from the gemspec really the right solution?
I'm still confused, as I was using the same version of Rubygems all along. (Though maybe there's a gem system update hidden away in the build somewhere.)
ok, removing the date from the gemspec fixed it. But would be nice to have this fixed on the original gem.
@ajsharp According to https://github.com/rubygems/rubygems/blob/master/lib/rubygems/specification.rb it's not deprecated.
These files are generated by calling rubygem's Specification#to_ruby method, so not being able to parse it's own output would indicate a rubygems bug.