And that turned out to be fixable with a global search and replace of "
00:00:00.000000000Z" to "" in my gemspecs. Rock. :)
On 9/7/11 8:39 AM, Ed Heil wrote:
Thanks, that worked!
On the downside, all my gems *except* camping now emit "invalid
gemspec" messages whenever I require rubygems... But I assume at this
point the issue is nothing to do with Camping and will see if I can
google me up an answer. (I wonder if it's OK to just delete all those
gemspecs? I don't actually know how gems work in any detail....)
On 9/7/11 2:31 AM, Magnus Holm wrote:
On Wed, Sep 7, 2011 at 04:35, Ed Heil<[email protected]> wrote:
Gave this a shot, and now when I run Camping I get:
Invalid gemspec in
[/Library/Ruby/Gems/1.8/specifications/camping-2.1.448.gemspec]:
Illformed
requirement ["#<YAML::Syck::DefaultKey:0x1023bfdc8> 0.8.7"]
Is that bad?
Try to upgrade RubyGems:
sudo gem update --system
It's this bug that's causing it:
http://blog.rubygems.org/2011/08/31/shaving-the-yaml-yacc.html
_______________________________________________
Camping-list mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/camping-list
_______________________________________________
Camping-list mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/camping-list