Rubygems isn't a gem, so that wouldn't work. I suppose I could package it up as one, but that defeats the purpose anyway.
-Nick On Wed, Jul 29, 2009 at 2:35 PM, Oren Teich <[email protected]> wrote: > > Have you tried putting the gem in your .gems file instead? > > I know that works well for rails (just specify rails -v 2.3.3 for > example), but haven't tried it with rubygems myself. > > Oren > > On Jul 29, 2009, at 7:01 AM, Nick Quaranto wrote: > > > > > Hey folks, I'm wondering if Rubygems could get upgraded on the Heroku > > systems to 1.3.3 or greater, the latest version (1.3.5) would be best. > > Gemcutter ( http://gemcutter.org ) depends on the latest version, and > > currently I'm getting around that by tossing the code in my lib > > directory and requiring in what I need to override it. However, > > something is definitely going wrong with that when trying to push to > > gemcutter (see the segfault?): > > > > ==> log/server_33403_23bb188_e4eb_54790.log <== > > /usr/local/lib/ruby/gems/1.8/gems/actionpack-2.3.2/lib/ > > action_controller/vendor/rack-1.0/rack.rb:17: warning: already > > initialized constant VERSION > > ./lib/rubygems.rb:193: warning: already initialized constant MUTEX > > ./lib/rubygems.rb:195: warning: already initialized constant > > RubyGemsPackageVersion > > ./lib/rubygems.rb:207: warning: already initialized constant > > WIN_PATTERNS > > ./lib/rubygems.rb:1078: warning: already initialized constant > > MARSHAL_SPEC_DIR > > ./lib/rubygems.rb:1083: warning: already initialized constant > > YAML_SPEC_DIR > > ./lib/rubygems/platform.rb:171: warning: already initialized constant > > RUBY > > ./lib/rubygems/platform.rb:177: warning: already initialized constant > > CURRENT > > ./lib/rubygems/source_index.rb:587: warning: already initialized > > constant Cache > > ./lib/rubygems/version.rb:246: warning: already initialized constant > > Requirement > > ./lib/rubygems/version.rb:36: [BUG] Segmentation fault > > ruby 1.8.6 (2008-08-11) [x86_64-linux] > > > >>> Thin web server (v1.0.1 codename ?) > >>> Maximum connections set to 1024 > >>> Listening on 0.0.0.0:54790, CTRL+C to stop > > /usr/local/bin/thin_launcher: line 5: 19862 Aborted > > thin -p $1 -e $RACK_ENV -R /home/heroku_rack/heroku.ru start >$2 2>&1 > > > > > > The strange part is that pushing was working a few days ago, this > > seems to be a relatively recent issue. I think upgrading to the latest > > recommended version of Rubygems is a good decision overall and I'd > > like to make sure that this isn't the cause for this bug. Thanks! > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~----------~----~----~----~------~----~------~--~---
