Open jarib opened 13 years ago
I have tried rubgems 1.8.10 and it creates the following date:
(ffrank@ffrank:spruz [master] ❷@spruz ->0)$ ruby -v ; gem -v ; tar xfO pkg/spruz-0.2.14.gem metadata.gz | zcat | grep ^date
ruby 1.9.2p290 (2011-07-09 revision 32553) [x86_64-darwin10.8.0]
1.8.10
date: 2011-09-01 00:00:00.000000000Z
Isn't this the output that is supposed to be 2011-09-01 according to the discussion under https://github.com/rubygems/rubygems/pull/57?
Yeah... I'm honestly not sure what's going on.
Is there an update on this issue? I'm also getting the error on a windows system. ruby 1.8.7
Also getting the error with watir-webdriver 0.3.2
Looks like spruz-0.2.13 is affected by this:
http://help.rubygems.org/discussions/problems/575-invalid-gemspec-with-invalid-date-format-in-specification
http://pastie.org/2462514
Any chance of a re-release to help users avoid this issue? If I understand things correctly, releasing with a more recent Rubygems or using the
YAML::ENGINE.yamler = 'syck'
workaround would resolve this.