Package Details: mongodb 7.0.14-1

Git Clone URL: https://aur.archlinux.org/mongodb.git (read-only, click to copy)
Package Base: mongodb
Description: A high-performance, open source, schema-free document-oriented database
Upstream URL: https://www.mongodb.com/
Keywords: database document-oriented
Licenses: SSPL-1.0
Provides: mongodb
Submitter: felixonmars
Maintainer: JstKddng
Last Packager: JstKddng
Votes: 35
Popularity: 0.072272
First Submitted: 2019-01-18 22:08 (UTC)
Last Updated: 2024-09-24 02:53 (UTC)

Sources (9)

Pinned Comments

JstKddng commented on 2022-08-03 23:28 (UTC)

Binary builds are available:

https://software.opensuse.org//download.html?project=home%3Ajustkidding%3Aarch&package=mongodb

JstKddng commented on 2022-08-03 23:28 (UTC)

If you have a pre-sandybridge CPU or an ARMv8 sbc, you can use mongodb44

If you'd like to stay in the V5.0 branch, you can use mongodb50

JstKddng commented on 2022-08-03 23:25 (UTC)

The mongo utility will be removed in future releases. Switching to mongosh is recommended.

Latest Comments

« First ‹ Previous 1 .. 6 7 8 9 10 11 12 13 14 15 Next › Last »

jamespharvey20 commented on 2019-08-21 22:40 (UTC)

READ ME - 4.2.0 is here - The good, the bad, and the ugly

Good! 4.2.0 finally supports python3. The dependency on aur/python2-scons is no longer needed.

Bad! 4.2.0 breaks having aur/wiredtiger as a separate package, so it is no longer needed. Upstream may fix this some day, but advised for now they can't be separate. When mongodb is being built, it recognizes it's not using a separate wiredtiger package and compiles wiredtiger's source into part of mongodb, so it's still there, just not separate. This increases the space required to about 260GB. The combined amount of time it takes to build shouldn't change.

Mixed! 4.2.0 breaks most of the tests performed in check() under devtools. Previously, only 8 tests couldn't run within devtools due to systemd-nspawn banning mlock(). Now, it appears hundreds of them require mlock(). It's no longer feasible to discover and disable all of them, and maintain this list between versions, so if devtools is detected, check() does nothing. In my opinion, that's bad news, because I'd like to run the tests. Many users will probably greatly welcome this change, because most of the space and time required to build mongodb is in check().

So, users of devtools will only need 20GB available to build this, and it will complete in about 30% of the time it used to, due to check() not doing anything.

But, direct users of makepkg (including probably most AUR helpers) will now need about 260GB available just to build this.

jamespharvey20 commented on 2019-08-20 01:26 (UTC)

@ectospasm, you're getting that building mongodb? Do you have python2-scons 3.1.1-1 (latest) installed, or an older version? What are you using to build? I just built python2-scons 3.1.1-1 then mongodb 4.0.12-2 in clean chroots (using devtools) and didn't get the error you posted.

In case this is due to using an older version of python2-scons, I just pushed an update to the PKGBUILD, to explicitly require version 3.1.1 or higher of python2-scons. I purposely didn't bump pkgrel in this push, because there's no need for anyone to re-compile who successfully did before. It's only useful to anyone failing to compile with this error. If you're using any aur helpers, please make sure they update to the newest PKGBUILD with this explicit version dependency.

ectospasm commented on 2019-08-18 20:22 (UTC) (edited on 2019-08-19 22:18 (UTC) by ectospasm)

I'm getting the following, it appears related to python2-scons:

python2-scons ==>; Starting build()...
Traceback (most recent call last):
  File "/usr/bin/scons2", line 204, in <module>;
    SCons.Script.main()
AttributeError: 'module' object has no attribute 'main'
==>; ERROR: A failure occurred in build().
    Aborting...

I've also reported this on the python2-scons AUR page.

jamespharvey20 commented on 2019-08-15 02:10 (UTC)

Thanks jokke, pushed fix to work with aur/python2-scons renaming of its binaries, done so it no longer conflicts with extra/scons.

Upstream released 4.2.0 a couple of days ago. It causes two compilation failures, which is why I haven't released it. Upstream says they arguably should test building with compilation options to use dependencies as already installed system libraries, rather than obtaining and compiling each of its dependencies on its own. But, as of now, they don't do this before releases.

Upstream released a working patch in my https://jira.mongodb.org/browse/SERVER-42787 which cleanly applies to 4.2.0, fixing an immediate compilation error.

I'm waiting to hear back on my https://jira.mongodb.org/browse/SERVER-42813. Somewhat late in compilation, there's an error along the lines of part of the mongoDB compilation is expecting to have built wiredtiger from source itself rather than using the system library. I am hopeful they will resolve this quickly like with the first ticket, and that this will be the last compilation error. If they don't do so quickly, I'll likely release 4.2.0 which will build at least wiredtiger internally from source, and remove it as a dependency. (At least building all dependencies internally from source expands the space needed to build from 180GB to 260GB, so I'd prefer not to have to do this.)

jokke commented on 2019-08-12 15:46 (UTC) (edited on 2019-08-12 15:50 (UTC) by jokke)

This would probably already do the trick. Haven't tried yet though

diff --git a/.SRCINFO b/.SRCINFO
index 4226b0e..4efcc77 100644
--- a/.SRCINFO
+++ b/.SRCINFO
@@ -0,0 +1,2 @@
+# Generated by mksrcinfo v8
+# Mon Aug 12 15:45:30 UTC 2019
@@ -4 +6 @@ pkgbase = mongodb
-   pkgrel = 1
+   pkgrel = 2
diff --git a/PKGBUILD b/PKGBUILD
index f88d835..3731d15 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -13 +13 @@ pkgver=4.0.12
-pkgrel=1
+pkgrel=2
@@ -79 +79 @@ build() {
-  scons core "${_scons_args[@]}"
+  scons2 core "${_scons_args[@]}"
@@ -87 +87 @@ check() {
-  scons unittests "${_scons_args[@]}"
+  scons2 unittests "${_scons_args[@]}"
@@ -105 +105 @@ check() {
-  scons dbtest "${_scons_args[@]}"
+  scons2 dbtest "${_scons_args[@]}"
@@ -108 +108 @@ check() {
-  scons integration_tests "${_scons_args[@]}"
+  scons2 integration_tests "${_scons_args[@]}"
@@ -115 +115 @@ package() {
-  scons install --prefix="${pkgdir}/usr" "${_scons_args[@]}"
+  scons2 install --prefix="${pkgdir}/usr" "${_scons_args[@]}"

jokke commented on 2019-08-11 10:57 (UTC)

Still fails to build after python2-scons changed the names of the binaries to include the suffix "2". e.g. scons2. See the PKGBUILD of python2-scons for more info.

jamespharvey20 commented on 2019-08-10 02:46 (UTC) (edited on 2019-08-21 22:41 (UTC) by jamespharvey20)

EDIT: Outdated as of 4.2.0. Left here for historical purposes only.

READ ME - aur/python2-scons is now required

The new dependency takes a while to compile, sorry.

extra/scons was based on python2 until its new release 4 days ago, 3.1.0-2. Now, it's based on python3. Upstream's build process is incompatible with python3, explaining why the previously succeeding build now fails. The first failure you run into is the SyntaxError: invalid syntax in SConstruct, in comments below.

There's 2 ways forward: 1. Patch in python3 support. 2. Require aur/python2-scons.

I'm going with option #2. Upstream has had merge requests open for several years adding support for python3, and they don't seem to care about it, because no comments have been on it for a year and a half now. See https://github.com/mongodb/mongo/pull/1216 and https://github.com/mongodb/mongo/pull/1195

If it were just a few small changes, I'd consider patching it in. Looking through these pull requests, it's at least hundreds of lines, maybe thousands, they aren't approved by upstream, and they don't apply cleanly to current versions.

yavorski commented on 2019-08-09 14:09 (UTC)

==> Starting build()...
scons: Reading SConscript files ...
  File "/home/lambda/dev/aur/mongodb/src/mongodb-src-r4.0.11/SConstruct", line 909

    print( "python version: " + " ".join( [ `i` for i in sys.version_info ] ) )

                                            ^

SyntaxError: invalid syntax

==> ERROR: A failure occurred in build().
    Aborting...

gazro commented on 2019-08-09 13:29 (UTC)

line 909

print( "python version: " + " ".join( [ `i` for i in sys.version_info ] ) )

                                        ^

SyntaxError: invalid syntax

==> ERROR: A failure occurred in build(). Aborting...