tag:help.rubygems.org,2010-01-19:/discussions/problems/680-invalid-gemspec-and-invalid-date-format-in-specification-2011-05-03-000000000000000zRubyGems.org: Discussion 2012-08-04T18:39:28Ztag:help.rubygems.org,2010-01-19:Comment/89293592011-07-28T12:51:27Z2011-07-28T12:51:29Zinvalid gemspec and invalid date format in specification: "2011-05-03 00:00:00.000000000Z"<div><p>I uninstalled the merb_datamapper as shown below BUT I STLL GET
THE ERROR</p>
<p>gino@gino-laptop:~/railsDEV$ sudo gem uninstall
merb_datamapper<br>
[sudo] password for gino: Invalid gemspec in
[/usr/local/lib/ruby/gems/1.8/specifications/merb_datamapper-1.1.3.gemspec]:
invalid date format in specification: "2011-05-03
00:00:00.000000000Z"<br>
Invalid gemspec in
[/usr/local/lib/ruby/gems/1.8/specifications/merb_datamapper-1.1.3.gemspec]:
invalid date format in specification: "2011-05-03
00:00:00.000000000Z"</p>
<p>You have requested to uninstall the gem:</p>
<pre>
<code>merb_datamapper-1.1.2</code>
</pre>
<p>merb-1.1.3 depends on [merb_datamapper (~> 1.1)]<br>
If you remove this gems, one or more dependencies will not be
met.<br>
Continue with Uninstall? [Yn] Y<br>
Successfully uninstalled merb_datamapper-1.1.2<br>
gino@gino-laptop:~/railsDEV$ gem list<br>
Invalid gemspec in
[/usr/local/lib/ruby/gems/1.8/specifications/merb_datamapper-1.1.3.gemspec]:
invalid date format in specification: "2011-05-03
00:00:00.000000000Z"</p></div>ginost7tag:help.rubygems.org,2010-01-19:Comment/89293592011-07-29T15:35:45Z2011-07-29T15:35:45Zinvalid gemspec and invalid date format in specification: "2011-05-03 00:00:00.000000000Z"<div><p>Not sure what's up with this, but it might be because you're
using 1.8.8. I would suggest sticking with 1.8.7 or 1.9.2. Also, if
you use RVM it's easier to isolate and recover from these problems
(make a gemset, blow it away if one gem is bad)</p></div>Nick Quarantotag:help.rubygems.org,2010-01-19:Comment/89293592011-08-05T07:48:07Z2011-08-05T07:48:08Zinvalid gemspec and invalid date format in specification: "2011-05-03 00:00:00.000000000Z"<div><p>It is a problem with the YAML parser used, either syck or psych
have troubles reading that date format. It has been popping up all
over the place for me recently.</p></div>Martin Wawruschtag:help.rubygems.org,2010-01-19:Comment/89293592011-08-05T10:24:31Z2011-08-05T10:24:31Zinvalid gemspec and invalid date format in specification: "2011-05-03 00:00:00.000000000Z"<div><p>Could you please explain how i could fix the YAML parser. Sorry
im new to<br>
rails</p>
<p>gino</p></div>gino ahmadtag:help.rubygems.org,2010-01-19:Comment/89293592011-08-05T10:27:23Z2011-08-05T10:27:26Zinvalid gemspec and invalid date format in specification: "2011-05-03 00:00:00.000000000Z"<div><p>Take a look at my reply here:</p>
<p><a href=
"https://github.com/sstephenson/execjs/issues/33#issuecomment-1733646">
https://github.com/sstephenson/execjs/issues/33#issuecomment-1733646</a></p>
<p>the bottom half of my comment explains what you need to do to
get this working.</p></div>Martin Wawruschtag:help.rubygems.org,2010-01-19:Comment/89293592011-12-18T20:11:36Z2011-12-18T20:11:36Zinvalid gemspec and invalid date format in specification: "2011-05-03 00:00:00.000000000Z"<div><p>We fixed a lot of these bad YAML/gemspec issues...is this still
happening anyone?</p></div>Nick Quarantotag:help.rubygems.org,2010-01-19:Comment/89293592011-12-22T13:49:06Z2011-12-22T18:23:17Zinvalid gemspec and invalid date format in specification: "2011-05-03 00:00:00.000000000Z"<div><p>I just ran into this error today while moving from RVM to rbenv
using 1.9.2p290 and rubygems 1.8.13.</p>
<p>After running bundle install with bundler installing the gems to
the project's vendor directory, when I run bundle exec, the
following gems gave me this error:<br>
term-ansicolor-1.0.7<br>
tilt-1.3.3<br>
rack-cache-1.0.3<br>
jquery-rails-1.0.19</p>
<p>If you need more information let me know. I'd be happy to help,
just not sure where to start.</p></div>mattottotag:help.rubygems.org,2010-01-19:Comment/89293592011-12-22T14:56:26Z2011-12-22T14:56:26Zinvalid gemspec and invalid date format in specification: "2011-05-03 00:00:00.000000000Z"<div><p>You can solve that by doing two things:</p>
<p>1) Update bundler to latest version</p>
<p>2) Perform <code>gem pristine <gemname></code> to restore
the gemspec of each of<br>
the faulty gems.</p>
<p>E.g.:</p>
<p>gem pristine term-ansicolor tilt rack-cache jquery-rails</p>
<p>HTH,</p></div>Luis Lavenatag:help.rubygems.org,2010-01-19:Comment/89293592012-02-09T02:54:58Z2012-02-09T02:54:59Zinvalid gemspec and invalid date format in specification: "2011-05-03 00:00:00.000000000Z"<div><p>Yes this error is still happening in spades. In fact, I got the
error for gemcutter:<br>
<code>Invalid gemspec in
[/var/lib/gems/1.8/specifications/gemcutter-0.7.1.gemspec]: invalid
date format in specification: "2011-12-02
00:00:00.000000000Z"</code> I read that I should update my version
of rubygems, but when I typed in "gem update --system" It told me
that I shouldn't update using that command because it would mess-up
my debian. So I used "apt-get", and it told me I have the latest
version.</p>
<p>So in other words, if you install ubuntu with the latest copies
of rubygems and gemcutter, you'll get an error.</p></div>Eric Cunninghamtag:help.rubygems.org,2010-01-19:Comment/89293592012-02-09T19:15:52Z2012-02-09T19:15:52Zinvalid gemspec and invalid date format in specification: "2011-05-03 00:00:00.000000000Z"<div><p>Unfortunately <code>gem pristine</code> won't fix this since
pristine only fixes installed gems and due to the invalid gemspec,
RubyGems doesn't think the gem is installed.</p>
<p><code>gem install gemcutter -v 0.7.1</code> will fix your
problem.</p></div>Eric Hodel