© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
Likely we should remove juju-mongodb3.2 from bionic once we actually have an alternative and can trust that it actually works. It is my understanding that 3.2 FTBFS and nobody was willing to maintain it.
Given the option, yes we would prefer a 3.4 without the JS engine. My understanding is that nobody was willing to build the package and the person on our team that had done it in the past (mwh) has left the team and no longer has time to maintain it.
The only package that anyone has put the effort into building was Mongolian 3.4.7 synced from debian, and so we asked to split it.
As for 3.6 vs 3.4, porting to 3.4 was not trivial though it wasn't a lot of changes. I would expect another amount of work to support 3.6. We'd probably be willing to do that work, but only if we could actually get something.
AIUI one of the primary reasons JS was removed was actually because of non amd64 arch compiling issues. So it may be that a 3.6 w/o JS would be easier to compile/maintain.
But we don't have the experience in-Juju (nor a MOTU). So 3.4 synced from debian seemed the best we could do.