Bug 471442 - Rails fails to run due to rake version error
Summary: Rails fails to run due to rake version error
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: rubygem-rails
Version: el5
Hardware: All
OS: Linux
medium
high
Target Milestone: ---
Assignee: Michael Stahnke
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-11-13 18:30 UTC by Joshua Baker-LePain
Modified: 2008-11-13 21:56 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2008-11-13 21:49:45 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Joshua Baker-LePain 2008-11-13 18:30:12 UTC 
User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.0.2) Gecko/2008092318 Fedora/3.0.2-1.fc9 Firefox/3.0.2

When I attempt to run the command 'rails', I get the following output:
/usr/lib/ruby/site_ruby/1.8/rubygems.rb:578:in `report_activate_error': RubyGem version error: rake(0.7.3 not >= 0.8.1) (Gem::LoadError)
        from /usr/lib/ruby/site_ruby/1.8/rubygems.rb:134:in `activate'
        from /usr/lib/ruby/site_ruby/1.8/rubygems.rb:158:in `activate'
        from /usr/lib/ruby/site_ruby/1.8/rubygems.rb:157:in `each'
        from /usr/lib/ruby/site_ruby/1.8/rubygems.rb:157:in `activate'
        from /usr/lib/ruby/site_ruby/1.8/rubygems.rb:49:in `gem'
        from /usr/bin/rails:15


Reproducible: Always

Steps to Reproduce:
1. yum install rubygem-rails
2. 'rails'
Comment 1 Joshua Baker-LePain 2008-11-13 19:05:36 UTC 
I just rpmbuilt the F8 src RPM for rubygem-rake-0.8.3-1 and rails seems happy now.  Is the rake version bump all that's needed?
Comment 2 Michael Stahnke 2008-11-13 20:19:47 UTC 
That's probably all that's needed.  I'll try to bump tonight.
Comment 3 Michael Stahnke 2008-11-13 21:49:16 UTC 
This is actually already built, it's just not in Stable.  Try the following.



yum --enablerepo='epel-testing' install rubygem-rake
Comment 4 Joshua Baker-LePain 2008-11-13 21:56:32 UTC 
Looks great -- thanks for the quick response!
Note You need to log in before you can comment on or make changes to this bug.