This bug was fixed in the package juju-mongodb3.2 - 3.2.9-0ubuntu1 --------------- juju-mongodb3.2 (3.2.9-0ubuntu1) yakkety; urgency=medium
* New upstream release. (LP: #1605976) (again) * Drop one part of s390x-support.patch that was included upstream. -- Michael Hudson-Doyle <[email protected]> Tue, 30 Aug 2016 11:40:44 +1200 ** Changed in: juju-mongodb3.2 (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1605976 Title: [2.0] bump mongod to 3.2.9 Status in juju: Triaged Status in juju-mongodb3.2 package in Ubuntu: Fix Released Status in juju-mongodb3.2 source package in Xenial: In Progress Bug description: We're a little behind on point releases for Mongo and apparently the difference is all about production quality :) Have noticed a couple of mongo-going-insane situations in testing, let's rev to 3.2.8 please and see how that fares. [Test Case] TBD [Regression Potential] Slight. juju-mongodb3.2 is only used by juju, and there have been several successful unit test runs with juju-mongodb3.2 3.2.8, e.g. http://data.vapour.ws/juju-ci/products/version-4299/run-unit-tests-yakkety-amd64/build-197/consoleText To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1605976/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : [email protected] Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
