rack 1.2 version causing misleading error msg

rack 1.2 version causing misleading error msg

[Don Park]

The problem: (note this is the only ruby on the system and rvm/bundler
is not being used)

$ gem list rails

*** LOCAL GEMS ***
rails (2.3.10, 2.3.8, 2.3.5)

$ unicorn_rails
I, [2010-11-23T15:03:12.134222 #1297]  INFO -- : listening on
addr=0.0.0.0:8080 fd=3
I, [2010-11-23T15:03:12.134499 #1297]  INFO -- : worker=0 spawning...
I, [2010-11-23T15:03:12.136120 #1300]  INFO -- : worker=0 spawned
pid=1300
I, [2010-11-23T15:03:12.136507 #1300]  INFO -- : Refreshing Gem list
I, [2010-11-23T15:03:12.136374 #1297]  INFO -- : master process ready
Missing the Rails 2.3.10 gem. Please `gem install -v=2.3.10 rails`,
update your RAILS_GEM_VERSION setting in config/environment.rb for the
Rails version you do have installed, or comment out RAILS_GEM_VERSION to
use the latest version installed.

After much experimentation, the problem is the existence of rack 1.2.1

$ sudo gem uninstall rack

Select gem to uninstall:
 1. rack-1.1.0
 2. rack-1.2.1
 3. All versions
> 2

donp@donpdonp:~/everyonedelivers$ unicorn_rails
I, [2010-11-23T15:26:40.729596 #2202]  INFO -- : listening on
addr=0.0.0.0:8080 fd=3
I, [2010-11-23T15:26:40.729869 #2202]  INFO -- : worker=0 spawning...
I, [2010-11-23T15:26:40.731081 #2204]  INFO -- : worker=0 spawned
pid=2204
I, [2010-11-23T15:26:40.731263 #2204]  INFO -- : Refreshing Gem list
I, [2010-11-23T15:26:40.734943 #2202]  INFO -- : master process ready

worker=0 ready



_______________________________________________
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Do not quote signatures (like this one) or top post when replying

Re: rack 1.2 version causing misleading error msg

[Eric Wong]

Don Park <don.park@gmail.com> wrote:

  Received: from rubyforge.org (rubyforge.org [127.0.0.1])
    by rubyforge.org (Postfix) with ESMTP id 79A9E1858112;
    Mon, 28 Feb 2011 12:12:48 -0500 (EST)
  Received: from mail-fx0-f50.google.com (mail-fx0-f50.google.com
    [209.85.161.50])
    by rubyforge.org (Postfix) with ESMTP id ADC541858112
    for <mongrel-unicorn@rubyforge.org>;
    Mon, 28 Feb 2011 11:23:10 -0500 (EST)
  Received: by fxm18 with SMTP id 18so4518682fxm.23
    for <mongrel-unicorn@rubyforge.org>;
    Mon, 28 Feb 2011 08:23:09 -0800 (PST)
  Received: by 10.223.114.203 with SMTP id f11mr509500faq.20.1298910133851;
    Mon, 28 Feb 2011 08:22:13 -0800 (PST)
  Received: from [10.0.1.104] (173-8-218-204-Oregon.hfc.comcastbusiness.net
    [173.8.218.204])
    by mx.google.com with ESMTPS id 21sm1637322fav.41.2011.02.28.08.22.11
    (version=SSLv3 cipher=OTHER); Mon, 28 Feb 2011 08:22:12 -0800 (PST)
  Date: Tue, 23 Nov 2010 15:36:36 -0800

Btw, something with your local mail queue is off, and it's not
Rubyforge's (nor Google's fault).

> The problem: (note this is the only ruby on the system and rvm/bundler
> is not being used)
> 
> $ gem list rails
> 
> *** LOCAL GEMS ***
> rails (2.3.10, 2.3.8, 2.3.5)
> 
> $ unicorn_rails
> Missing the Rails 2.3.10 gem. Please `gem install -v=2.3.10 rails`,
> update your RAILS_GEM_VERSION setting in config/environment.rb for the
> Rails version you do have installed, or comment out RAILS_GEM_VERSION to
> use the latest version installed.
> 
> After much experimentation, the problem is the existence of rack 1.2.1
> 
> $ sudo gem uninstall rack
> 
> Select gem to uninstall:
>  1. rack-1.1.0
>  2. rack-1.2.1
>  3. All versions
> > 2
> 
> donp@donpdonp:~/everyonedelivers$ unicorn_rails

<snip> yup, all is good when only one version of Rack is installed.

This should be fixed in RubyGems 1.6:
  http://blog.segment7.net/2011/02/19/rubygems-gem-activation-is-changing

I'm sure the RubyGems testers would appreciate all the testing/feedback
they can get with this since it's been a problem for a while (though
things like bundler/isolate do a great deal to mitigate the issue).

-- 
Eric Wong
_______________________________________________
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Do not quote signatures (like this one) or top post when replying