Comment 8 for bug 1271937

well, bugger.

On Sat, Mar 15, 2014 at 10:03 AM, Curtis Hovey <email address hidden> wrote:

> juju-mongodb support was removed several revisions ago. hacks like
> symlinks to the installed juju-mongodb are required to make juju think a
> monogodb-server is installed.
>
> Proper juju-mongodb support will be added at the state-server level. The
> feature was reverted because the cli assumed that the local presence of
> juju-mongodb meant that it was also on the bootstrap node.
>
> --
> You received this bug notification because you are subscribed to juju-
> core.
> Matching subscriptions: MOAR JUJU SPAM!
> https://bugs.launchpad.net/bugs/1271937
>
> Title:
> Use juju-mongodb when the package is available
>
> Status in juju-core:
> In Progress
>
> Bug description:
> juju-mongodb is ready for use with trusty. James Page suggests that
> jujud install juju-mongodb when the package is available, then
> fallback to mongodb-server. This allows us to backport jujuj-mongodb
> in the future.
>
> Fixing this issue may be an opportunity to address bug 1240667. As I
> understand it, that bug wants the rules to change when selecting
> mongodb-server to ensure the version comes from the cloud-archive
> (because the cloud-archive should have a lower priority)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju-core/+bug/1271937/+subscriptions
>