Bug 1231409

Summary: rubygem-rspec-3.3.0 is available
Product: [Fedora] Fedora Reporter: Upstream Release Monitoring <upstream-release-monitoring>
Component: rubygem-rspecAssignee: Michael Stahnke <mastahnke>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: mastahnke, mmorsi, s, vondruch
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: rubygem-rspec-3.3.0-1.fc23 Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-08-10 10:04:37 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
[patch] Update to 3.3.0 (#1231409) none

Description Upstream Release Monitoring 2015-06-13 01:21:31 UTC 
Latest upstream release: 3.3.0
Current version/release in rawhide: 3.2.0-1.fc22
URL: http://rubygems.org/gems/rspec

Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy

More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring

Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.
Comment 1 Upstream Release Monitoring 2015-06-13 01:21:42 UTC 
Created attachment 1038208 [details]
[patch] Update to 3.3.0 (#1231409)
Comment 2 Upstream Release Monitoring 2015-06-13 01:23:39 UTC 
Scratch build succeeded http://koji.fedoraproject.org/koji/taskinfo?taskID=10036963
Comment 3 Upstream Release Monitoring 2015-08-02 07:25:48 UTC 
mtasaka's rubygem-rspec-3.3.0-1.fc24 completed http://koji.fedoraproject.org/koji/buildinfo?buildID=674885
Comment 4 Fedora Update System 2015-08-04 13:05:19 UTC 
rubygem-rspec-3.3.0-1.fc23, rubygem-rspec-mocks-3.3.2-2.fc23, rubygem-rspec-core-3.3.2-2.fc23, rubygem-rspec-support-3.3.0-2.fc23, rubygem-rspec-expectations-3.3.1-2.fc23, rubygem-rspec-rails-3.3.3-1.fc23 has been submitted as an update for Fedora 23.
https://admin.fedoraproject.org/updates/FEDORA-2015-12671/rubygem-rspec-3.3.0-1.fc23,rubygem-rspec-support-3.3.0-2.fc23,rubygem-rspec-mocks-3.3.2-2.fc23,rubygem-rspec-expectations-3.3.1-2.fc23,rubygem-rspec-core-3.3.2-2.fc23,rubygem-rspec-rails-3.3.3-1.fc23
Comment 5 Fedora Update System 2015-08-05 00:11:44 UTC 
Package rubygem-rspec-3.3.0-1.fc23, rubygem-rspec-mocks-3.3.2-2.fc23, rubygem-rspec-core-3.3.2-2.fc23, rubygem-rspec-support-3.3.0-2.fc23, rubygem-rspec-expectations-3.3.1-2.fc23, rubygem-rspec-rails-3.3.3-1.fc23:
* should fix your issue,
* was pushed to the Fedora 23 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing rubygem-rspec-3.3.0-1.fc23 rubygem-rspec-mocks-3.3.2-2.fc23 rubygem-rspec-core-3.3.2-2.fc23 rubygem-rspec-support-3.3.0-2.fc23 rubygem-rspec-expectations-3.3.1-2.fc23 rubygem-rspec-rails-3.3.3-1.fc23'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2015-12671/rubygem-rspec-3.3.0-1.fc23,rubygem-rspec-support-3.3.0-2.fc23,rubygem-rspec-mocks-3.3.2-2.fc23,rubygem-rspec-expectations-3.3.1-2.fc23,rubygem-rspec-core-3.3.2-2.fc23,rubygem-rspec-rails-3.3.3-1.fc23
then log in and leave karma (feedback).
Comment 6 Fedora Update System 2015-08-10 10:04:37 UTC 
rubygem-rspec-3.3.0-1.fc23, rubygem-rspec-mocks-3.3.2-2.fc23, rubygem-rspec-core-3.3.2-2.fc23, rubygem-rspec-support-3.3.0-2.fc23, rubygem-rspec-expectations-3.3.1-2.fc23, rubygem-rspec-rails-3.3.3-1.fc23 has been pushed to the Fedora 23 stable repository.  If problems still persist, please make note of it in this bug report.