mongodb release 2.0.1 version and mark it as production release: http://www.mongodb.org/downloads Reproducible: Always mongodb is nosql database which used by many servers
Created attachment 291595 [details] A starting point for a working ebuild
Created attachment 291597 [details] Adapted patch from the patches intended for 1.8.4 This doesn't work, yet. The compile fails with the following messages: third_party/pcre-7.4/pcre_exec.c: In function 'int match(const unsigned char*, const uschar*, const uschar*, int, match_data*, long unsigned int, eptrblock*, int, unsigned int)': third_party/pcre-7.4/pcre_exec.c:691:1: error: jump to label 'L_RM1' third_party/pcre-7.4/pcre_exec.c:4248:1: error: from here third_party/pcre-7.4/pcre_exec.c:690:9: error: skips initialization of 'heapframe* newframe' third_party/pcre-7.4/pcre_exec.c:750:1: error: jump to label 'L_RM2' third_party/pcre-7.4/pcre_exec.c:4248:1: error: from here third_party/pcre-7.4/pcre_exec.c:749:7: error: skips initialization of 'heapframe* newframe' third_party/pcre-7.4/pcre_exec.c:792:1: error: jump to label 'L_RM3' third_party/pcre-7.4/pcre_exec.c:4248:1: error: from here third_party/pcre-7.4/pcre_exec.c:791:7: error: skips initialization of 'heapframe* newframe' third_party/pcre-7.4/pcre_exec.c:883:1: error: jump to label 'L_RM4' . . . and so on. Help would be much appreciated :)
Hey Is someone handle this bug?
Sorry for not responding in a timely fashion. The issue is basically that upstream has decided to statically link pcre, spidemonkey and so on. This is something we're not very happy with – especially when the statically linked version of pcre had security issues. When discussing with upstream, they told us that a patch would occur in the next minor (2.0.1), which unfortunately didn't. They have now moved it to 2.0.2 (see https://jira.mongodb.org/browse/SERVER-3829) ; so the bump eagerly awaits this patch. See http://groups.google.com/group/mongodb-dev/browse_thread/thread/38e8c30606a300c3 for relevant discussion. The best thing to do if you want to help out is either help with convincing upstream about the importance of letting us maintain shared libraries ourselves, or help out with a patch to SConstruct that helps us do this. See above bug url for this. Thanks for your interest. We're all eagerly awaiting feedback.
Hey Thanks for your reply. Could we make version bump with hard mask package?? Thanks
(In reply to comment #5) > Hey > Thanks for your reply. > Could we make version bump with hard mask package?? > Thanks As soon as a scones patch lands, I'll be happy to bump this. Feel free to help out!
Well, they promise to deliver 2.0.2 no later than the next tuesday... https://jira.mongodb.org/browse/SERVER?report=com.atlassian.jira.plugin.system.project:roadmap-panel
I indeed asked them if they felt like they'll honor this deadline, I got no reply so far. So I guess we'll have to hope for a good news tomorrow :)
Here is Eliot Horowitz comment about the version patch: https://jira.mongodb.org/browse/SERVER-3829?focusedCommentId=66691&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-66691
(In reply to comment #9) > Here is Eliot Horowitz comment about the version patch: > https://jira.mongodb.org/browse/SERVER-3829?focusedCommentId=66691&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-66691 Yes, and I've tested successfully the building on a snapshot ebuild. I'm now waiting for upstream to tag a version past this commit so I can get a fixed ebuild number. I'll keep this bug posted, thanks.
Hey fellows, while we wait for an official tag/backport I pushed a snapshot version of current git master so you can all give it a try. Please note that required spidermonkey is now <1.8 +*mongodb-2.0.2_pre20111116 (16 Nov 2011) + + 16 Nov 2011; Ultrabug <ultrabug@gentoo.org> + +mongodb-2.0.2_pre20111116.ebuild, +files/mongodb-2.0-fix-scons.patch: + Bump for 2.x pre-release version. +
This line in your ebuild if [[ ${REPLACING_VERSIONS} < 1.8 ]]; then should be replaced by if [[ ${REPLACING_VERSIONS} < 2.0 ]]; then Final tagging of 2.0.2 should be around the corner.
(In reply to comment #12) > This line in your ebuild > if [[ ${REPLACING_VERSIONS} < 1.8 ]]; then > should be replaced by > if [[ ${REPLACING_VERSIONS} < 2.0 ]]; then > > Final tagging of 2.0.2 should be around the corner. Hi mate, thanks for your comment. IMHO, the < 1.8 is correct because according to the 2.0 release notes [1], upgrading from 1.8 is seamless and you don't need to run mongod --upgrade. So this statement remains true if you come from < 1.8 versions. And yeah, I hope the tagging comes soon :) [1] http://www.mongodb.org/display/DOCS/2.0+Release+Notes#2.0ReleaseNotes-Upgrading Cheers
I cannot say but that you're right (it crssed my mind, but was too lazy to actually check). Sorry for the noise...
Hey guys, I'm glad to announce the so awaited 2.0.2_rc0 ebuild ;) +*mongodb-2.0.2_rc0 (18 Nov 2011) + + 18 Nov 2011; Ultrabug <ultrabug@gentoo.org> -mongodb-1.8.2-r1.ebuild, + -mongodb-2.0.2_pre20111116.ebuild, +mongodb-2.0.2_rc0.ebuild, + files/mongodb-2.0-fix-scons.patch: + Version bump, drop old + Thanks to everyone for their interest and their help in voting it to upstream.
