Description: A high-performance, open source, schema-free document-oriented database
| releases | alpha | amd64 | arm | hppa | ia64 | mips | ppc | ppc64 | ppc macos | s390 | sh | sparc | x86 | USE-Flags | dependencies | ebuild warnings |
|---|
| mongodb-3.4.9 |
- | ~ | - | - | - | - | - | - | - | - | - | - | ~ | debug
kerberos
libressl
mms-agent
ssl
test
+tools
| show | To upgrade from a version earlier than the 3.0-series, you must
successively upgrade major releases until you have upgraded
to 3.2-series. Then upgrade to 3.4 series.
!! IMPORTANT !!
${PN} configuration files have changed !
Make sure you migrate from /etc/conf.d/${PN} to the new YAML standard in /etc/${PN}.conf
http://docs.mongodb.org/manual/reference/configuration-options/
Make sure you also follow the upgrading process :
http://docs.mongodb.org/master/release-notes/3.0-upgrade/
MongoDB 3.0 introduces the WiredTiger storage engine.
WiredTiger is incompatible with MMAPv1 and you need to dump/reload your data if you want to use it.
Once you have your data dumped, you need to set storage.engine: wiredTiger in /etc/${PN}.conf
http://docs.mongodb.org/master/release-notes/3.0-upgrade/#change-storage-engine-to-wiredtiger
Make sure to read the release notes and follow the upgrade process:
https://docs.mongodb.org/manual/release-notes/3.4/
https://docs.mongodb.com/manual/release-notes/3.4/#upgrade-procedures
|
| mongodb-3.4.7 |
- | ~ | - | - | - | - | - | - | - | - | - | - | ~ | debug
kerberos
libressl
mms-agent
ssl
test
+tools
| show | To upgrade from a version earlier than the 3.0-series, you must
successively upgrade major releases until you have upgraded
to 3.2-series. Then upgrade to 3.4 series.
!! IMPORTANT !!
${PN} configuration files have changed !
Make sure you migrate from /etc/conf.d/${PN} to the new YAML standard in /etc/${PN}.conf
http://docs.mongodb.org/manual/reference/configuration-options/
Make sure you also follow the upgrading process :
http://docs.mongodb.org/master/release-notes/3.0-upgrade/
MongoDB 3.0 introduces the WiredTiger storage engine.
WiredTiger is incompatible with MMAPv1 and you need to dump/reload your data if you want to use it.
Once you have your data dumped, you need to set storage.engine: wiredTiger in /etc/${PN}.conf
http://docs.mongodb.org/master/release-notes/3.0-upgrade/#change-storage-engine-to-wiredtiger
Make sure to read the release notes and follow the upgrade process:
https://docs.mongodb.org/manual/release-notes/3.4/
https://docs.mongodb.com/manual/release-notes/3.4/#upgrade-procedures
|
| mongodb-3.4.6 |
- | ~ | - | - | - | - | - | - | - | - | - | - | ~ | debug
kerberos
libressl
mms-agent
ssl
test
+tools
| show | To upgrade from a version earlier than the 3.0-series, you must
successively upgrade major releases until you have upgraded
to 3.2-series. Then upgrade to 3.4 series.
!! IMPORTANT !!
${PN} configuration files have changed !
Make sure you migrate from /etc/conf.d/${PN} to the new YAML standard in /etc/${PN}.conf
http://docs.mongodb.org/manual/reference/configuration-options/
Make sure you also follow the upgrading process :
http://docs.mongodb.org/master/release-notes/3.0-upgrade/
MongoDB 3.0 introduces the WiredTiger storage engine.
WiredTiger is incompatible with MMAPv1 and you need to dump/reload your data if you want to use it.
Once you have your data dumped, you need to set storage.engine: wiredTiger in /etc/${PN}.conf
http://docs.mongodb.org/master/release-notes/3.0-upgrade/#change-storage-engine-to-wiredtiger
Make sure to read the release notes and follow the upgrade process:
https://docs.mongodb.org/manual/release-notes/3.4/
https://docs.mongodb.com/manual/release-notes/3.4/#upgrade-procedures
|
| mongodb-3.4.4 |
- | ~ | - | - | - | - | - | - | - | - | - | - | ~ | debug
kerberos
libressl
mms-agent
ssl
test
+tools
| show | To upgrade from a version earlier than the 3.0-series, you must
successively upgrade major releases until you have upgraded
to 3.2-series. Then upgrade to 3.4 series.
!! IMPORTANT !!
${PN} configuration files have changed !
Make sure you migrate from /etc/conf.d/${PN} to the new YAML standard in /etc/${PN}.conf
http://docs.mongodb.org/manual/reference/configuration-options/
Make sure you also follow the upgrading process :
http://docs.mongodb.org/master/release-notes/3.0-upgrade/
MongoDB 3.0 introduces the WiredTiger storage engine.
WiredTiger is incompatible with MMAPv1 and you need to dump/reload your data if you want to use it.
Once you have your data dumped, you need to set storage.engine: wiredTiger in /etc/${PN}.conf
http://docs.mongodb.org/master/release-notes/3.0-upgrade/#change-storage-engine-to-wiredtiger
Make sure to read the release notes and follow the upgrade process:
https://docs.mongodb.org/manual/release-notes/3.4/
https://docs.mongodb.com/manual/release-notes/3.4/#upgrade-procedures
|
| mongodb-3.4.3 |
- | ~ | - | - | - | - | - | - | - | - | - | - | ~ | debug
kerberos
libressl
mms-agent
ssl
test
+tools
| show | To upgrade from a version earlier than the 3.0-series, you must
successively upgrade major releases until you have upgraded
to 3.2-series. Then upgrade to 3.4 series.
!! IMPORTANT !!
${PN} configuration files have changed !
Make sure you migrate from /etc/conf.d/${PN} to the new YAML standard in /etc/${PN}.conf
http://docs.mongodb.org/manual/reference/configuration-options/
Make sure you also follow the upgrading process :
http://docs.mongodb.org/master/release-notes/3.0-upgrade/
MongoDB 3.0 introduces the WiredTiger storage engine.
WiredTiger is incompatible with MMAPv1 and you need to dump/reload your data if you want to use it.
Once you have your data dumped, you need to set storage.engine: wiredTiger in /etc/${PN}.conf
http://docs.mongodb.org/master/release-notes/3.0-upgrade/#change-storage-engine-to-wiredtiger
Make sure to read the release notes and follow the upgrade process:
https://docs.mongodb.org/manual/release-notes/3.4/
https://docs.mongodb.com/manual/release-notes/3.4/#upgrade-procedures
|
| mongodb-3.2.16 |
- | ~ | - | - | - | - | - | - | - | - | - | - | ~ | debug
kerberos
libressl
mms-agent
ssl
test
+tools
| show | To upgrade an existing MongoDB deployment to 3.2, you must be
running a 3.0-series release. Please update to the latest 3.0
release before continuing if wish to keep your data.
!! IMPORTANT !!
${PN} configuration files have changed !
Make sure you migrate from /etc/conf.d/${PN} to the new YAML standard in /etc/${PN}.conf
http://docs.mongodb.org/manual/reference/configuration-options/
Make sure you also follow the upgrading process :
http://docs.mongodb.org/master/release-notes/3.0-upgrade/
MongoDB 3.0 introduces the WiredTiger storage engine.
WiredTiger is incompatible with MMAPv1 and you need to dump/reload your data if you want to use it.
Once you have your data dumped, you need to set storage.engine: wiredTiger in /etc/${PN}.conf
http://docs.mongodb.org/master/release-notes/3.0-upgrade/#change-storage-engine-to-wiredtiger
Make sure to read the release notes and follow the upgrade process:
https://docs.mongodb.org/manual/release-notes/3.2/
https://docs.mongodb.org/master/release-notes/3.2-upgrade/
Starting in 3.2, MongoDB uses the WiredTiger as the default storage engine.
|
| mongodb-3.2.13 |
- | ~ | - | - | - | - | - | - | - | - | - | - | ~ | debug
kerberos
libressl
mms-agent
ssl
test
+tools
| show | To upgrade an existing MongoDB deployment to 3.2, you must be
running a 3.0-series release. Please update to the latest 3.0
release before continuing if wish to keep your data.
!! IMPORTANT !!
${PN} configuration files have changed !
Make sure you migrate from /etc/conf.d/${PN} to the new YAML standard in /etc/${PN}.conf
http://docs.mongodb.org/manual/reference/configuration-options/
Make sure you also follow the upgrading process :
http://docs.mongodb.org/master/release-notes/3.0-upgrade/
MongoDB 3.0 introduces the WiredTiger storage engine.
WiredTiger is incompatible with MMAPv1 and you need to dump/reload your data if you want to use it.
Once you have your data dumped, you need to set storage.engine: wiredTiger in /etc/${PN}.conf
http://docs.mongodb.org/master/release-notes/3.0-upgrade/#change-storage-engine-to-wiredtiger
Make sure to read the release notes and follow the upgrade process:
https://docs.mongodb.org/manual/release-notes/3.2/
https://docs.mongodb.org/master/release-notes/3.2-upgrade/
Starting in 3.2, MongoDB uses the WiredTiger as the default storage engine.
|
| mongodb-3.2.12 |
- | ~ | - | - | - | - | - | - | - | - | - | - | ~ | debug
kerberos
libressl
mms-agent
ssl
test
+tools
| show | To upgrade an existing MongoDB deployment to 3.2, you must be
running a 3.0-series release. Please update to the latest 3.0
release before continuing if wish to keep your data.
!! IMPORTANT !!
${PN} configuration files have changed !
Make sure you migrate from /etc/conf.d/${PN} to the new YAML standard in /etc/${PN}.conf
http://docs.mongodb.org/manual/reference/configuration-options/
Make sure you also follow the upgrading process :
http://docs.mongodb.org/master/release-notes/3.0-upgrade/
MongoDB 3.0 introduces the WiredTiger storage engine.
WiredTiger is incompatible with MMAPv1 and you need to dump/reload your data if you want to use it.
Once you have your data dumped, you need to set storage.engine: wiredTiger in /etc/${PN}.conf
http://docs.mongodb.org/master/release-notes/3.0-upgrade/#change-storage-engine-to-wiredtiger
Make sure to read the release notes and follow the upgrade process:
https://docs.mongodb.org/manual/release-notes/3.2/
https://docs.mongodb.org/master/release-notes/3.2-upgrade/
Starting in 3.2, MongoDB uses the WiredTiger as the default storage engine.
|
| mongodb-3.0.15 |
- | ~ | - | - | - | - | - | - | - | - | - | - | ~ | debug
kerberos
libressl
mms-agent
ssl
+tools
| show | !! IMPORTANT !!
${PN} configuration files have changed !
Make sure you migrate from /etc/conf.d/${PN} to the new YAML standard in /etc/${PN}.conf
http://docs.mongodb.org/manual/reference/configuration-options/
Make sure you also follow the upgrading process :
http://docs.mongodb.org/master/release-notes/3.0-upgrade/
MongoDB 3.0 introduces the WiredTiger storage engine.
WiredTiger is incompatible with MMAPv1 and you need to dump/reload your data if you want to use it.
Once you have your data dumped, you need to set storage.engine: wiredTiger in /etc/${PN}.conf
http://docs.mongodb.org/master/release-notes/3.0-upgrade/#change-storage-engine-to-wiredtiger
|
| mongodb-3.0.14 |
- | + | - | - | - | - | - | - | - | - | - | - | + | debug
kerberos
libressl
mms-agent
ssl
+tools
| show | !! IMPORTANT !!
${PN} configuration files have changed !
Make sure you migrate from /etc/conf.d/${PN} to the new YAML standard in /etc/${PN}.conf
http://docs.mongodb.org/manual/reference/configuration-options/
Make sure you also follow the upgrading process :
http://docs.mongodb.org/master/release-notes/3.0-upgrade/
MongoDB 3.0 introduces the WiredTiger storage engine.
WiredTiger is incompatible with MMAPv1 and you need to dump/reload your data if you want to use it.
Once you have your data dumped, you need to set storage.engine: wiredTiger in /etc/${PN}.conf
http://docs.mongodb.org/master/release-notes/3.0-upgrade/#change-storage-engine-to-wiredtiger
|
| mongodb-2.6.12 |
- | + | - | - | - | - | - | - | - | - | - | - | + | debug
kerberos
mms-agent
ssl
static-libs
| show | !! IMPORTANT !!
${PN} configuration files have changed !
Make sure you migrate from /etc/conf.d/${PN} to the new YAML standard in /etc/${PN}.conf
http://docs.mongodb.org/manual/reference/configuration-options/
Make sure you also follow the upgrading process :
http://docs.mongodb.org/master/release-notes/2.6-upgrade/
MMS Agent configuration file has been moved to :
/etc/mms-agent.conf
|
some ebuild warning depend on specific use-flags or architectures, all ebuild-warnings are shown.
| 
| 
- Running on 
-
:
: 
