Bug 1350958

Summary: Update the EPEL7 version of mongodb to 2.6.12 to match upstream, receive fixes
Product: [Fedora] Fedora EPEL Reporter: Thomas Boutell <tom>
Component: mongodbAssignee: Marek Skalický <mskalick>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: epel7CC: admiller, bretm, carlwgeorge, jdornak, johan.o.hedin, jpacner, mskalick, npmccallum, strobert, tdawson
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: mongodb-2.6.12-2.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-09-06 04:18:26 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Thomas Boutell 2016-06-28 20:18:04 UTC 
Description of problem:

MongoDB 2.6.12 has been out since March and addresses a number of bugs, please release in EPEL. Thank you.
Comment 1 Fedora Update System 2016-08-08 11:48:25 UTC 
mongodb-2.6.12-2.el7 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-5c31722250
Comment 2 Marek Skalický 2016-08-08 11:50:14 UTC 
Sorry for such late reply. MongoDB 2.6.12 should be build in EPEL7 for x86_64.

You can test it in bodhi.
Comment 3 Fedora Update System 2016-08-09 02:19:17 UTC 
mongodb-2.6.12-2.el7 has been pushed to the Fedora EPEL 7 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-5c31722250
Comment 4 Fedora Update System 2016-09-06 04:18:21 UTC 
mongodb-2.6.12-2.el7 has been pushed to the Fedora EPEL 7 stable repository. If problems still persist, please make note of it in this bug report.