Skip to content
New issue

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

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Invalid gemspec on rubygems 1.8.6 #99

Closed
ajsharp opened this issue Oct 1, 2011 · 8 comments
Closed

Invalid gemspec on rubygems 1.8.6 #99

ajsharp opened this issue Oct 1, 2011 · 8 comments

Comments

@ajsharp
Copy link

ajsharp commented Oct 1, 2011

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"

@ajsharp
Copy link
Author

ajsharp commented Oct 1, 2011

Apparently you're not supposed to specify the date in the gemspec anymore. Sounds like an easy fix.

ajsharp added a commit to ajsharp/json that referenced this issue Oct 1, 2011
@etdsoft
Copy link

etdsoft commented Oct 10, 2011

Hi,

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?

Thanks!

@duelinmarkers
Copy link

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?

@ajsharp
Copy link
Author

ajsharp commented Jan 4, 2012

The date field has been deprecated in the gem spec.

Alex Sharp

Zaarly, Inc.
@ajsharp | github.com/ajsharp | alexjsharp.com

On Jan 4, 2012, at 5:30 AM, John Humereply@reply.github.com wrote:

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?


Reply to this email directly or view it on GitHub:
#99 (comment)

@duelinmarkers
Copy link

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.)

@gamafranco
Copy link

ok, removing the date from the gemspec fixed it. But would be nice to have this fixed on the original gem.

@flori
Copy link
Owner

flori commented May 9, 2012

@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.

@hsbt
Copy link
Collaborator

hsbt commented Feb 23, 2021

RubyGems 1.x is EOL status in 2021.

@hsbt hsbt closed this as completed Feb 23, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants