Public bug reported:
# juju-mongodb3.2
The Juju team wants juju-mongodb3.2 packaged in xenial.
lp:~sinzui/ubuntu/xenial/juju-mongodb3.2/xenial-mongodb-3.2
This package is an fork and upgrade of the juju-mongodb2.6 package
that will be used in upgrades. There is a lot of change in this package
because Upstream changed a lot. the package required new rules and
deps. Many patches were needed to support wily/xenial tools chains
and arm64 and ppc64el archs.
Juju2 prefers juju-mongodb3.2 as the db for its controllers. This db
uses a different storage engine named wiredtiger. it requires JS to
operate.
There are many packages in src/third_party/. Most of them are ignored
because we choose to use the ubuntu system packages. Wiretiger appears
in third_party. 10gen/MongoDB bought the product and made it the default
storage engine. We must use this version. Mongo builds with the
embedded mozjs, there is no system option.
## juju-mongodb2.6-to-juju-mongodb3.2.diff
This is a diff of the debian dir from juju-mongodb2.6 to
juju-mongodb3.2, excluding patches. The principal changes are:
1. Rename juju-mongodb2.6 => juju-mongodb3.2.
2. Added new build deps. I tried to use system packages when possible.
- trusty's libboost is too old so d/rules falls back to the embedded
package for trusty only.
- server-js is off; the server does not accept js queries, but the
wiredtiger storage engine is compiled with JS, the server uses
JS to talk to talk internally to the storage engine. The
--js-engine=none option removes all js and only comppiles a server
with the old storage engine.
3. The test infastructure also changed alot. We run only part of the
test suite because the full suite will test JS communication from
client to server, and we do not support that scenario.
## juju-mongodb3.2-patches.diff
There are three general kinds of change to patches.
1. The patch was upstreamed, or obsoleted by the removal of files to
patch:
-00git_boost_1.56.patch
-0006-Fix-ARM-alignment-problems.patch
-0007-Use-TIME_UTC_-macro.patch
-0009-ignore-unused-local-typedefs.patch
-# Added for arm64 and ppc64el enablement
-0001-Add-option-to-disable-javascript.patch
-0004-Support-ppc64el-builds.patch
-0099-Pagesize-hacks.patch
-fix-yaml-detection.patch
-no-unused-function.patch
2. Patches found upstream in the devel release 3.3
+scons-detect-ppc64.patch
+support-ppc64el-mozjs.patch
+use-4kb-sector-size-for-direct-io.patch
+fix-debug-non-jit-builds-of-spidermonkey.patch
+processinfo_test-fails-on-ppc64.patch
+dont-assume-char-is-unsigned-in-logging.patch
+use-signed-char-explicitly.patch
+warn-user-if-locked-memory-limit-is-too-low.patch
3. Patches created by me to address wily/xenial build and test issues
+offset-outside-of-bounds.patch
These tests fail to build on wily and xenial. They are fine on
trusty
+fix-ppc64-preprocessor-blocks.patch
A synax error only seen when attempting to build wiredtiger on
ppc64el.
+skip-high-mem-test.patch
The warn-user-if-locked-memory-limit-is-too-low patch does not
fix the test, it just suggests the user get more memory and
fails. the test will not pass on the builders of on the ppc64el
quests I have.
+arm64-immediate-delete-should-wait-cursor.patch
I disabled the test because it fails on arm64.
** Affects: juju-mongodb (Ubuntu)
Importance: Undecided
Status: New
** Tags: needs-packaging
** Attachment added: "juju-mongodb2.6-to-juju-mongodb3.2.diff"
https://bugs.launchpad.net/bugs/1557852/+attachment/4600706/+files/juju-mongodb2.6-to-juju-mongodb3.2.diff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-mongodb in Ubuntu.
https://bugs.launchpad.net/bugs/1557852
Title:
[needs-packaging] juju-mongodb3.2 in xenial, wily, and trusty
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-mongodb/+bug/1557852/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
