Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

current gem release has an invalid gemspec #1

brianmario opened this Issue May 17, 2011 · 8 comments


None yet
4 participants

The date in the gemspec should be something like "2011-05-15" but the currently released version has some time info on it too and rubygems is blowing up about it :P


mislav commented May 19, 2011

The time + zone info in the newest gemspec is a product of rubygems 1.8. I tried installing this gem with RubyGems 1.5.3 and it doesn't choke. Which version of rubygems chokes on this spec?

In any case, this is a rubygems bug. I could try to work around it by building a new gem using an older version of RubyGems.

@mislav mislav closed this May 19, 2011

Ah, I think at the time I was using 1.8 but I downgraded to 1.7.2 and it seems to barf still.
Been thinking about switching to slimgems, have you tried that out yet?


mislav commented May 20, 2011

If you're still having issues I can republish the gem using older rubygems. I wouldn't like to do so for each of my gems, tho.

Didn't know about slimgems. Have to check it out

I switched to it yesterday, so far so good. (and this problem went away as a result)

@mislav we're seeing the same error

$ gem -v
Invalid gemspec in [/home/deploy/.rvm/gems/ruby-1.9.2-p180/specifications/faraday-0.7.3.gemspec]: invalid date format in specification: "2011-06-27 00:00:00.000000000Z"

@mislav mislav reopened this Jul 3, 2011


mislav commented Jul 3, 2011

Gosh this is the most annoying bug in rubygems lately. I had to republish several of my gems just to get rid of these. I thought that the newest 1.8 release takes care of this.

I'll see what I can do.

pi3r commented Jul 8, 2011

@mislav same error as @svenfuchs.

Invalid gemspec in [/usr/local/lib/ruby/gems/1.9.1/specifications/faraday-0.7.3.gemspec]: invalid date format in specification: "2011-06-27 00:00:00.000000000Z"

@mislav mislav closed this in 6cf599c Jul 8, 2011


mislav commented Jul 8, 2011

So, when you release a gem from ruby 1.9 and have libyaml on your machine, gem specs are serialized to yaml by psych and the date is saved in a format that syck parser cannot grok and older rubygems choke onto.

This isn't even fixed in rubygems master. I had to write a wrapper script for gem just so I could force the yamler to be syck and build new versions of Faraday and faraday-stack gems for you guys. Try em out

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment