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

Closed
tanelsuurhans opened this issue Jul 20, 2011 · 4 comments
Closed

Invalid Gemspec #6

tanelsuurhans opened this issue Jul 20, 2011 · 4 comments

Comments

@tanelsuurhans
Copy link

Getting this error every time the project is loaded (and all the gems):
Invalid gemspec in [/Users/tanel/.rvm/gems/ruby-1.9.2-p180@project/specifications/active_reload-0.2.0.gemspec]: invalid date format in specification: "2011-07-20 00:00:00.000000000Z"

The gemspec itself looks like this at that location:

-- encoding: utf-8 --

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

s.required_rubygems_version = Gem::Requirement.new(">= 0") if s.respond_to? :required_rubygems_version=
s.authors = ["Robert Pankowecki"]
s.date = %q{2011-07-20 00:00:00.000000000Z}
s.description = %q{Reload Rails code in development mode only when change is deteced}
s.email = ["robert.pankowecki@gmail.com"]
s.homepage = %q{https://github.com/paneq/active_reload}
s.require_paths = ["lib"]
s.rubyforge_project = %q{active_reload}
s.rubygems_version = %q{1.7.2}
s.summary = %q{Reload Rails code in development mode only when change is deteced}

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<rake>, [">= 0"])
  s.add_development_dependency(%q<bbq>, [">= 0"])
else
  s.add_dependency(%q<rake>, [">= 0"])
  s.add_dependency(%q<bbq>, [">= 0"])
end

else
s.add_dependency(%q, [">= 0"])
s.add_dependency(%q, [">= 0"])
end
end

The date clearly is in the wrong format, but the gemspec does not resemble the one in your repository.
Do you use something else to generate the gemspec before releasing?

@paneq
Copy link
Owner

paneq commented Jul 20, 2011

I check my local version of this file /home/rupert/.rvm/gems/ruby-1.9.2-p290-fastrequire/specifications/active_reload-0.2.0.gemspec and the date line looks normal:

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

  s.required_rubygems_version = Gem::Requirement.new(">= 0") if s.respond_to? :required_rubygems_version=
  s.authors = ["Robert Pankowecki"]
  s.date = %q{2011-07-20}
  s.description = %q{Reload Rails code in development mode only when change is deteced}
  s.email = ["robert.pankowecki@gmail.com"]
  s.has_rdoc = nil
  s.homepage = %q{https://github.com/paneq/active_reload}
  s.require_paths = ["lib"]
  s.rubyforge_project = %q{active_reload}
  s.rubygems_version = %q{1.6.2}
  s.summary = %q{Reload Rails code in development mode only when change is deteced}

  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<rake>, [">= 0"])
      s.add_development_dependency(%q<bbq>, [">= 0"])
    else
      s.add_dependency(%q<rake>, [">= 0"])
      s.add_dependency(%q<bbq>, [">= 0"])
    end
  else
    s.add_dependency(%q<rake>, [">= 0"])
    s.add_dependency(%q<bbq>, [">= 0"])
  end
end

Try removing and installing the gem again. Maybe that will help. So far I am not able to reproduce.

@paneq
Copy link
Owner

paneq commented Jul 23, 2011

@tanelsuurhans - Any news on this issue? Did you try to reinstall?

@paneq
Copy link
Owner

paneq commented Jul 31, 2011

I'm closing because I was not able to reproduce the bug and you did not provide further information required to any kind of investigation. I assume that it works for you fine now. Nobody else reported such problem so I think that it was some kind of single issue.

@paneq paneq closed this as completed Jul 31, 2011
@tanelsuurhans
Copy link
Author

Sorry for the slow response. This seems to be caused by rubygems somehow, as updating it and then reinstalling the gem seemed to fix the issue.

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

2 participants