Bug 811711 - Update to version 2.0+ ?
Summary: Update to version 2.0+ ?
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: mongodb
Version: el6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Nathaniel McCallum
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-04-11 19:12 UTC by Pierre-YvesChibon
Modified: 2014-02-04 09:37 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-02-04 09:37:37 UTC
Type: Bug


Attachments (Terms of Use)

Description Pierre-YvesChibon 2012-04-11 19:12:56 UTC
I was wondering if there has been thoughts/consideration on updating the mongodb package for EPEL6.

Similarly, I would be curious to know of reason not to do so.

I am asking this also based on the remark done around min 38 at this pycon talk:
 http://pyvideo.org/video/914/mongodb-and-python
The speaker says:
"in fact you should not be using a version before 2.0"

Thanks

Comment 1 Nathaniel McCallum 2012-04-17 17:16:39 UTC
Yes, there have been thoughts/consideration. I'd personally like to do it. However, in order for it to work we have to patch the JS engine. We have a patch we are currently shipping in Fedora which works. However, some of the MongoDB tests fail due to slightly different behavior changes in the latest mozjs release. See this bug for relevant info: https://jira.mongodb.org/browse/SERVER-4870

I don't believe there are any bugs in the *patch*, but just in different behavior with different versions of spidermonkey. You are welcome to try the 2.0.4 EL6 builds here http://koji.fedoraproject.org/koji/packageinfo?packageID=10883 but be aware you might hit bugs.

Comment 2 Felix Schwarz 2012-11-22 17:48:28 UTC
Looks like this was done already? EPEL 6 now ships MongoDB 2.0.7, right?

Comment 3 Matthias Saou 2014-02-04 09:37:37 UTC
Closing, since EPEL 6 indeed ships 2.x (currently 2.4).


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