databases/mongodb70: 7.0.45
Simple version bump.
Announcement:
https://www.mongodb.com/community/forums/t/mongodb-7-0-45-is-released/344297?u=r_k
Release Notes:
https://www.mongodb.com/docs/manual/release-notes/7.0/#7045---oct-13-2026
Security: Yes, see Release Notes for a list of CVEs.
databases/mongodb70: 7.0.43
Changes:
https://www.mongodb.com/docs/manual/release-notes/7.0/#7043---sept-11-2026
Security: CVE-2026-89099 "Race Condition in MongoDB Server Document Value Layer Leads to Memory Corruption"
databases/mongodb70: 7.0.41
Announcement:
https://www.mongodb.com/community/forums/t/mongodb-7-0-41-is-released/343299?u=r_k
Changes:
https://www.mongodb.com/docs/manual/release-notes/7.0#7041---sept-8-2026
Removed some python311 compatibility. Not needed anymore.
"REINPLACE_CMD ran, but did not modify file contents"
Security: a whole list of CVEs in the release notes
databases/mongodb70: 7.0.40
Announcement:
https://www.mongodb.com/community/forums/t/mongodb-7-0-40-is-released/342425?u=r_k
Release Notes:
https://www.mongodb.com/docs/manual/release-notes/7.0
Security: a whole list of CVEs in the release notes
databases/mongodb70: 7.0.39
Announcement:
https://www.mongodb.com/community/forums/t/mongodb-7-0-39-is-released/341747?u=r_k
Changelog:
https://www.mongodb.com/docs/manual/release-notes/7.0/#7.0.39---july-22--2026
Security: a whole list of CVEs in the changelog
databases/mongodb70: re-enable python3.12
The patch was disabled temporarily because it was in the way of the recent upgrades.
NB: a test build was already running when this PR came in.
- Remove jobs_unsafe from a flavour. The build timed out with this.
- no portrevision bump as no pkg content changes.
PR: 296127
databases/mongodb70: 7.0.37
Release Notes:
https://www.mongodb.com/docs/manual/release-notes/7.0/#7.0.37---june-11--2026
Important MongoDB patch available - June 2026:
https://www.mongodb.com/community/forums/t/important-mongodb-patch-available-june-2026/339979?u=r_k
Security: CVE-2026-11933
databases/mongodb70: 7.0.36
Release Notes:
https://www.mongodb.com/docs/manual/release-notes/7.0/#7.0.36---june-10--2026
- Reduced the amount of modification in patch-src_mongo_util_net_openssl__init.cpp
databases/mongodb70: 7.0.35
Release notes:
https://www.mongodb.com/docs/manual/release-notes/7.0/#7.0.35---june-9--2026
- gen-config.sh is move to scripts/gen-config.sh
- Patch added to circumvent these errors:
src/mongo/util/net/openssl_init.cpp:247:51: error: no member named 'opensslPrimaryDRBGReseedMaxRequests' in namespace 'mongo::crypto'
src/mongo/util/net/openssl_init.cpp:249:45: error: no member named 'opensslPrimaryDRBGReseedMaxTime' in namespace 'mongo::crypto'
- disabled PATCH_FILE for python3.12, didn't apply
- other patches just got a refresh
Security: CVE-2026-9740
Security: CVE-2026-9741
Security: CVE-2026-9746
Security: CVE-2026-9747
Security: CVE-2026-9748
Security: CVE-2026-9749
Security: CVE-2026-9750
Security: CVE-2026-9751
Security: CVE-2026-9752
Security: CVE-2026-9753
databases/mongodb70: fix build with clang 21
With clang 21 databases/mongodb70 fails to build, with errors similar to:
In file included from src/third_party/boost/libs/log/src/default_sink.cpp:20:
In file included from src/third_party/boost/boost/thread/locks.hpp:10:
In file included from src/third_party/boost/boost/thread/lock_algorithms.hpp:11:
In file included from src/third_party/boost/boost/thread/lock_types.hpp:18:
In file included from src/third_party/boost/boost/thread/thread_time.hpp:11:
In file included from src/third_party/boost/boost/date_time/posix_time/posix_time_types.hpp:16:
In file included from src/third_party/boost/boost/date_time/posix_time/posix_time_duration.hpp:15:
In file included from src/third_party/boost/boost/numeric/conversion/cast.hpp:33:
In file included from src/third_party/boost/boost/numeric/conversion/converter.hpp:13:
In file included from src/third_party/boost/boost/numeric/conversion/conversion_traits.hpp:13:
In file included from src/third_party/boost/boost/numeric/conversion/detail/conversion_traits.hpp:18:
In file included from src/third_party/boost/boost/numeric/conversion/detail/int_float_mixture.hpp:19:
In file included from src/third_party/boost/boost/mpl/integral_c.hpp:32:
src/third_party/boost/boost/mpl/aux_/integral_wrapper.hpp:62:51: error: in-class initializer for static data member is not a constant expression
62 | BOOST_STATIC_CONSTANT(AUX_WRAPPER_VALUE_TYPE, prior_value = BOOST_MPL_AUX_STATIC_CAST(AUX_WRAPPER_VALUE_TYPE, (N - 1)));
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
src/third_party/boost/boost/config/detail/suffix.hpp:394:72: note: expanded from macro 'BOOST_STATIC_CONSTANT'
394 | # define BOOST_STATIC_CONSTANT(type, assignment) static const type assignment
| ^~~~~~~~~~
src/third_party/boost/boost/log/utility/strictest_lock.hpp:70:53: note: in instantiation of template class 'mpl_::integral_c<boost::log::lock_access_mode, boost::log::unlocked_access>' requested here
70 | struct thread_access_mode_of< no_lock< MutexT > > : mpl::integral_c< lock_access_mode, unlocked_access >
| ^
src/third_party/boost/boost/mpl/aux_/integral_wrapper.hpp:62:65: note: integer value -1 is outside the valid range of values [0, 3] for the enumeration type 'lock_access_mode'
62 | BOOST_STATIC_CONSTANT(AUX_WRAPPER_VALUE_TYPE, prior_value = BOOST_MPL_AUX_STATIC_CAST(AUX_WRAPPER_VALUE_TYPE, (N - 1)));
| ^
src/third_party/boost/boost/mpl/aux_/static_cast.hpp:24:47: note: expanded from macro 'BOOST_MPL_AUX_STATIC_CAST'
24 | # define BOOST_MPL_AUX_STATIC_CAST(T, expr) static_cast<T>(expr)
| ^
There are two of these cases in the vendored copy of boost in mongodb70,
which have been fixed in boost upstream:
* https://github.com/boostorg/numeric_conversion/commit/50a1eae
* https://github.com/boostorg/log/commit/77f1e20
To fix the errors, port these patches back to the vendored boost.
PR: 293230
MFH: 2026Q1
databases/mongodb70: 7.0.29
Announcement:
https://www.mongodb.com/community/forums/t/mongodb-7-0-29-is-released/334623?u=r_k
Changelog:
https://www.mongodb.com/docs/manual/release-notes/7.0/#7.0.29---jan-27--2026
Security: a whole list of CVEs in the changelog
databases/mongodb70: harden the port to external CONFIGURE_ARGS
CONFIGURE_ARGS is directly connected to CONFIGURE_SCRIPT and the script
only accepts 2 parameters. Exit 1 on incorrect number of parameters.
And don't allow to += on CONFIGURE_ARGS.
Not bumping PORTREVISION, no content change intended.
PR: 291951
databases/mongodb70: make_jobs_unsafe
For unknown reasons this port tends to fail a lot on @armv80a flavor.
From the build log:
"scons: *** [build/opt/mongo/db/catalog/collection_uuid_mismatch.o] Error -9"
I can't reproduce this locally. Let's try to remove parallel jobs and
see if it improves the build stability.
Reported-by: https://portsfallout.com/fallout?port=databases%2Fmongodb%5B0-9%5D&maintainer=&env=&category=&flavor=
databases/mongodb[78]0: improve a patch
Be pedantic that '!= 0' is not the same as '== -1'. And indeed -1 is what
is documented in the man page of _umtx_op to indicate an error.
No functional change expected.
Reported by: https://github.com/mongodb/mongo/pull/1607#pullrequestreview-2677292316
databases/mongodb70: fix build with python 3.12
Requests by a user who custom builds this port with python 3.12.
Tested to still build with the currently default python 3.11.
PR: 289086
databases/mongodb70: 7.0.23
Includes patch to implement waitable atomics for FreeBSD for
https://jira.mongodb.org/browse/SERVER-81797.
This patch is developed by me. It did not go through QA of MongoDB Inc.
I asked to upstream the patch but they don't want to take responsibilty
for code they don't run themselves. (Which I can understand from their
perspective.)
https://github.com/mongodb/mongo/pull/1607#issuecomment-2996276435
https://jira.mongodb.org/browse/SERVER-99225
Anyway, this has run without errors for a while on my Raspberry Pi + net-mgmt/unifi9.
I don't have full QA in place and could only do limited testing. I can't
take any responsibilty for the quality of the patch.
Make backups and test for yourself in your setup before upgrading
any critical production environment.
Changes:
https://www.mongodb.com/docs/manual/release-notes/7.0/#7.0.23---aug-13--2025
Announcement:
https://www.mongodb.com/community/forums/t/mongodb-7-0-23-is-released/327242?u=r_k
databases/mongodb70: 7.0.20
Changes:
https://www.mongodb.com/docs/v7.0/release-notes/7.0/#7.0.20---apr-29--2025
Announcement:
https://www.mongodb.com/community/forums/t/mongodb-7-0-20-is-released/321461?u=r_k
- refactored do-configure to use HAS_CONFIGURE which properly passes CONFIGURE_ENV
- updates spidermonkey to MozJS 128.8-ESR
- needs cbindgen now
- pet portclippy and portfmt (moved vars around)
- replaced multiple paths with MOZJS_WRKSRC
- removed a mozjs patch which is in upstream now
databases/mongodb70: 7.0.19
Changes:
https://www.mongodb.com/docs/manual/release-notes/7.0/#7.0.19---apr-14--2025
"This release contains security or reliability improvements. These release notes will be updated when more information is available."
Security: details not known yet
databases/mongodb70: update to 7.0.17
Changes:
https://www.mongodb.com/docs/manual/release-notes/7.0/#7.0.17---feb-21--2025
https://www.mongodb.com/community/forums/t/mongodb-7-0-17-rc1-is-released/313042?u=r_k
- updated spidermonkey
- made check on spidermonkey revision more vebose to ease upgrades
databases/mongodb80: update to 8.0.5
Changes:
https://www.mongodb.com/docs/manual/release-notes/8.0/#8.0.5---feb-20--2025
https://www.mongodb.com/community/forums/t/mongodb-8-0-5-rc1-is-released/312357?u=r_k
- spidermonkey updated to 115.19.0esr (from esr115.7)
- be more verbose in pre-configure check so I don't need to lookup the new revision
databases/mongodb70: add flavor for RPI-compatible version
The default flavor is the upstream supported version. For older
ARM CPUs we have an -armv80a flavor now. MongoDB is known to be used by
net-mgmt/unifi* users on this hardware. MongoDB 6.0 is planned to go out
of support in July 2025 [1], so this is preparation to make MongoDB 7.0
the default dependency for Unifi.
[1] https://www.mongodb.com/legal/support-policy/lifecycles