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 #15

Closed
johncburr opened this issue Aug 16, 2011 · 6 comments
Closed

Invalid gemspec #15

johncburr opened this issue Aug 16, 2011 · 6 comments

Comments

@johncburr
Copy link

Did a bundle install of my app. It is now trying to use childprocess 0.2.1 instead of 0.1.9. Keep getting the following error:

Invalid gemspec in [/usr/lib/ruby/gems/1.8/specifications/childprocess-0.2.1.gemspec]: invalid date format in specification: "2011-08-11 00:00:00.000000000Z"

Did I do something wrong, or is that on your end?

@jarib
Copy link
Collaborator

jarib commented Aug 16, 2011

Hmm, not sure. Perhaps @drbrain can help? The installed .gemspec looks fine to me:

# -*- encoding: utf-8 -*-

Gem::Specification.new do |s|
  s.name = %q{childprocess}
  s.version = "0.2.1"

  s.required_rubygems_version = Gem::Requirement.new(">= 0") if s.respond_to? :required_rubygems_version=
  s.authors = [%q{Jari Bakken}]
  s.date = %q{2011-08-11}
  s.description = %q{This gem aims at being a simple and reliable solution for controlling external programs running in the background on any Ruby / OS combination.}
  s.email = [%q{jari.bakken@gmail.com}]
  s.homepage = %q{http://github.com/jarib/childprocess}
  s.require_paths = [%q{lib}]
  s.rubyforge_project = %q{childprocess}
  s.rubygems_version = %q{1.8.6}
  s.summary = %q{This gem aims at being a simple and reliable solution for controlling external programs running in the background on any Ruby / OS combination.}

  if s.respond_to? :specification_version then
    s.specification_version = 3

    if Gem::Version.new(Gem::VERSION) >= Gem::Version.new('1.2.0') then
      s.add_development_dependency(%q<rspec>, [">= 2.0.0"])
      s.add_development_dependency(%q<yard>, [">= 0"])
      s.add_development_dependency(%q<rake>, ["~> 0.9.2"])
      s.add_runtime_dependency(%q<ffi>, ["~> 1.0.6"])
    else
      s.add_dependency(%q<rspec>, [">= 2.0.0"])
      s.add_dependency(%q<yard>, [">= 0"])
      s.add_dependency(%q<rake>, ["~> 0.9.2"])
      s.add_dependency(%q<ffi>, ["~> 1.0.6"])
    end
  else
    s.add_dependency(%q<rspec>, [">= 2.0.0"])
    s.add_dependency(%q<yard>, [">= 0"])
    s.add_dependency(%q<rake>, ["~> 0.9.2"])
    s.add_dependency(%q<ffi>, ["~> 1.0.6"])
  end
end

@jarib
Copy link
Collaborator

jarib commented Aug 16, 2011

@peternixey
Copy link

I'm having a similar problem:

Installing childprocess (0.2.1) Invalid gemspec in [/Users/petenixey/.rvm/gems/ruby-1.9.2-p180@live/specifications/childprocess-0.2.1.gemspec]: invalid date format in specification: "2011-08-11 00:00:00.000000000Z"
/Users/petenixey/.rvm/rubies/ruby-1.9.2-p180/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:277:in `block in _resort!': undefined method `name' for nil:NilClass (NoMethodError)

@johncburr
Copy link
Author

I ended up just doing a sudo vim on the file and removing the offending timestamp. Then I did the bundle install the second time and it was fine.

@jarib - Thanks for the link, at least I know why it happened.

@jarib
Copy link
Collaborator

jarib commented Aug 26, 2011

I've released 0.2.2 with no changes except a new gemspec generated with rubygems 1.8.9 (previous gem was made with 1.8.6). Not sure if that helps, but hopefully it does.

@peternixey
Copy link

I think it was just an issue with rubygems: rubygems/rubygems#57. On updating it, all the problems went away (there were issues with several other gems too) @jarib - thank for the quick response

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

3 participants