Bug 747405 - rpms spec doesnt match gemspec (causes gem to not work)
Summary: rpms spec doesnt match gemspec (causes gem to not work)
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: rubygem-rspec-rails
Version: 16
Hardware: Unspecified
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Vít Ondruch
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-19 17:53 UTC by Jason Guiditta
Modified: 2011-10-25 03:21 UTC (History)
3 users (show)

Fixed In Version: rubygem-rspec-rails-2.6.1-3.fc16
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-10-25 03:21:38 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Jason Guiditta 2011-10-19 17:53:21 UTC
Description of problem: Dependency on rspec was changed to match our current fedora setup of 2.x subpackages, but 1.3.x rspec.  However, the gemfile itself was not changed to match, so when you try to load a test suite with rspec-rails, you get an error that you do not have rspec ~>2.6

Version-Release number of selected component (if applicable): rubygem-rspec-rails-2.6.1


How reproducible: 
Running rake spec from an app depending on rspec-rails

also you can see the dependency issue with:
 gem dependency rspec-rails



Steps to Reproduce:
1. on f16, you can yum install aeolus-all and aeolus-conductor-devel
2. cd to /usr/share/aeolus-conductor
3. as root, attempt to run 'rake spec'
  
Actual results:
 Could not find rspec (~> 2.6.0) 

Expected results: tests run


Additional info: This is a blocker for the aeolus project in f16, as we will not be able to have people run our test suite on test day next week if this is not fixed.  Help much appreciated.

Comment 1 Jason Guiditta 2011-10-19 18:15:41 UTC
Forgot to note, I edited my local gemspec as below, and things noow work as expected:

if Gem::Version.new(Gem::VERSION) >= Gem::Version.new('1.2.0') then
      s.add_runtime_dependency(%q<activesupport>, ["~> 3.0"])
      s.add_runtime_dependency(%q<actionpack>, ["~> 3.0"])
      s.add_runtime_dependency(%q<railties>, ["~> 3.0"])
      s.add_runtime_dependency(%q<rspec-core>, ["~> 2.6.0"])
      s.add_runtime_dependency(%q<rspec-mocks>, ["~> 2.6.0"])
      s.add_runtime_dependency(%q<rspec-expectations>, ["~> 2.6.0"])
    else
      s.add_dependency(%q<activesupport>, ["~> 3.0"])
      s.add_dependency(%q<actionpack>, ["~> 3.0"])
      s.add_dependency(%q<railties>, ["~> 3.0"])
      s.add_dependency(%q<rspec-core>, ["~> 2.6.0"])
      s.add_dependency(%q<rspec-mocks>, ["~> 2.6.0"])
      s.add_dependency(%q<rspec-expectations>, ["~> 2.6.0"])
    end
  else
    s.add_dependency(%q<activesupport>, ["~> 3.0"])
    s.add_dependency(%q<actionpack>, ["~> 3.0"])
    s.add_dependency(%q<railties>, ["~> 3.0"])
    s.add_dependency(%q<rspec-core>, ["~> 2.6.0"])
    s.add_dependency(%q<rspec-mocks>, ["~> 2.6.0"])
    s.add_dependency(%q<rspec-expectations>, ["~> 2.6.0"])
  end

Comment 2 Fedora Update System 2011-10-20 08:50:15 UTC
rubygem-rspec-rails-2.6.1-3.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/rubygem-rspec-rails-2.6.1-3.fc16

Comment 3 Vít Ondruch 2011-10-20 08:51:24 UTC
Jason,

Thank you for your report. I have applied the patch. Please try it and give it some karma.

Thank you.

Comment 4 Fedora Update System 2011-10-20 22:16:44 UTC
Package rubygem-rspec-rails-2.6.1-3.fc16:
* should fix your issue,
* was pushed to the Fedora 16 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing rubygem-rspec-rails-2.6.1-3.fc16'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2011-14687
then log in and leave karma (feedback).

Comment 5 Fedora Update System 2011-10-25 03:21:38 UTC
rubygem-rspec-rails-2.6.1-3.fc16 has been pushed to the Fedora 16 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.