backport juju-mongodb3.2 to 14.04
Bug #1620419 reported by
Michael Hudson-Doyle
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| juju-mongodb3.2 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
| Trusty |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
Juju 2.0 will be much easier to support on 14.04 if it can depend on juju-mongodb3.2 rather than the long since EOL juju-mongodb (aka 2.4). This means we need to build juju-mongodb3.2 in trusty of course, hence this bug. It builds fine, as can be seen at https:/
| Changed in juju-mongodb3.2 (Ubuntu): | |
| status: | New → Invalid |
| Changed in juju-mongodb3.2 (Ubuntu Trusty): | |
| status: | New → In Progress |
Revision history for this message
| Michael Hudson-Doyle (mwhudson) wrote | #1 |
| Changed in juju-mongodb3.2 (Ubuntu Trusty): | |
| status: | In Progress → Invalid |
To post a comment you must log in.
I got the wrong end of the stick, juju 2 is only going to trusty-backports so this is not needed.