Let''s say I have a pristine Unixy system in front of me. (In my case, it''s a new OS X 10.7 installation and I put MacPorts on there.) What is the simplest way to get an up-to-date Camping installation? (I''ve been out of the Ruby loop for a while.) -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/camping-list/attachments/20110829/56cb4b7e/attachment.html>
`gem install camping` :D (You may also want to install Markaby, ActiveRecord and all that.) -- -- Matma Rex
We definitely need to put out a new release. Try this in the meantime: gem install camping --source http://gems.judofyr.net/ (I''ve just updated the DNS record, so it might take an hour or two to propagate correctly) // Magnus Holm On Tue, Aug 30, 2011 at 07:09, John Beppu <john.beppu at gmail.com> wrote:> Let''s say I have a pristine Unixy system in front of me. (In my case, it''s > a new OS X 10.7 installation and I put MacPorts on there.) > > What is the simplest way to get an up-to-date Camping installation? > > (I''ve been out of the Ruby loop for a while.) > > > > _______________________________________________ > Camping-list mailing list > Camping-list at rubyforge.org > http://rubyforge.org/mailman/listinfo/camping-list >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/camping-list/attachments/20110830/5f373e12/attachment-0001.html>
On Tue, Aug 30, 2011 at 5:09 PM, John Beppu <john.beppu at gmail.com> wrote:> Let''s say I have a pristine Unixy system in front of me. ?(In my case, it''s > a new OS X 10.7 installation and I put MacPorts on there.) > What is the simplest way to get an up-to-date Camping installation? > (I''ve been out of the Ruby loop for a while.)step 1. Install RVM $ bash < <(curl -s https://rvm.beginrescueend.com/install/rvm) step 2. Install ruby rvm install 1.9.2 step 3. Install camping gem install camping. Voila!
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? On 8/30/11 3:18 AM, Magnus Holm wrote:> We definitely need to put out a new release. Try this in the meantime: > > gem install camping --source http://gems.judofyr.net/ > > (I''ve just updated the DNS record, so it might take an hour or two to > propagate correctly) > > // Magnus Holm > > > On Tue, Aug 30, 2011 at 07:09, John Beppu <john.beppu at gmail.com > <mailto:john.beppu at gmail.com>> wrote: > > Let''s say I have a pristine Unixy system in front of me. (In my > case, it''s a new OS X 10.7 installation and I put MacPorts on there.) > > What is the simplest way to get an up-to-date Camping installation? > > (I''ve been out of the Ruby loop for a while.) > > > > _______________________________________________ > Camping-list mailing list > Camping-list at rubyforge.org <mailto:Camping-list at rubyforge.org> > http://rubyforge.org/mailman/listinfo/camping-list > > > > > _______________________________________________ > Camping-list mailing list > Camping-list at rubyforge.org > http://rubyforge.org/mailman/listinfo/camping-list-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/camping-list/attachments/20110906/93197737/attachment.html>
Oh, this is on OS X -- Snow Leopard, using the built-in Ruby. On 8/30/11 3:18 AM, Magnus Holm wrote:> We definitely need to put out a new release. Try this in the meantime: > > gem install camping --source http://gems.judofyr.net/ > > (I''ve just updated the DNS record, so it might take an hour or two to > propagate correctly) > > // Magnus Holm > > > On Tue, Aug 30, 2011 at 07:09, John Beppu <john.beppu at gmail.com > <mailto:john.beppu at gmail.com>> wrote: > > Let''s say I have a pristine Unixy system in front of me. (In my > case, it''s a new OS X 10.7 installation and I put MacPorts on there.) > > What is the simplest way to get an up-to-date Camping installation? > > (I''ve been out of the Ruby loop for a while.) > > > > _______________________________________________ > Camping-list mailing list > Camping-list at rubyforge.org <mailto:Camping-list at rubyforge.org> > http://rubyforge.org/mailman/listinfo/camping-list > > > > > _______________________________________________ > Camping-list mailing list > Camping-list at rubyforge.org > http://rubyforge.org/mailman/listinfo/camping-list-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/camping-list/attachments/20110906/a98ea71b/attachment.html>
On Wed, Sep 7, 2011 at 04:35, Ed Heil <edheil at fastmail.fm> 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
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<edheil at fastmail.fm> 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 > Camping-list at rubyforge.org > http://rubyforge.org/mailman/listinfo/camping-list
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<edheil at fastmail.fm> 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 >> Camping-list at rubyforge.org >> http://rubyforge.org/mailman/listinfo/camping-list
On Wed, Sep 7, 2011 at 16:00, Ed Heil <edheil at fastmail.fm> wrote:> And that turned out to be fixable with a global search and replace of " > 00:00:00.000000000Z" to "" in my gemspecs. ?Rock. :)Great! Feel free to bother us more if you encounter more problems :)