Hide Forgot
Description of problem: Cucumber fails to start in rails applications if used in conjunction with cucumber-rails due to incompatible dependencies. It would be great if cucumber-rails would be updated to version 1.3.0 Version-Release number of selected component (if applicable): $ rpm -qa | grep cucumber rubygem-cucumber-1.1.9-1.fc17.noarch rubygem-cucumber-rails-1.0.2-9.fc17.noarch How reproducible: Install both rpms and running cucumber in any rails app will output: $ cucumber Using the default profile... Unable to activate cucumber-rails-1.0.2, because cucumber-1.1.9 conflicts with cucumber (~> 1.0.0) (Gem::LoadError) /usr/share/rubygems/rubygems/specification.rb:1655:in `raise_if_conflicts' /usr/share/rubygems/rubygems/specification.rb:746:in `activate' /usr/share/rubygems/rubygems.rb:212:in `rescue in try_activate' /usr/share/rubygems/rubygems.rb:209:in `try_activate' ... Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
So this is actually rubygem-cucumber-rails issue => assign to correct component.
rubygem-cucumber-rails-1.3.0-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/rubygem-cucumber-rails-1.3.0-1.fc17
Package rubygem-cucumber-rails-1.3.0-1.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing rubygem-cucumber-rails-1.3.0-1.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-11194/rubygem-cucumber-rails-1.3.0-1.fc17 then log in and leave karma (feedback).
rubygem-cucumber-rails-1.3.0-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.