Interim plan to move away from the mongo tarball

[Mark Ramm]

On 03/26/2013 09:26 AM, James Page wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> Hey Gustavo
>
> On 25/03/13 17:58, Gustavo Niemeyer wrote:
>> On Wed, Mar 20, 2013 at 1:31 AM, David Cheney
>> <david.cheney at canonical.com> wrote:
>>>> The short version (email me if you really want the whole
>>>> story).
>>>>
>>>> By Raring we hope to have mongo 2.2+ssl in a package for P, Q
>>>> and R and a large amount of resources have been mobilised to
>>>> making this happen, but that is only 1/2 the story.
>> That's a nice advancement, and a major undertaking at this point.
>>
>> One of the reasons for the out-of-band tarball was that it gave us
>> an easy way to have the same MongoDB version running on all past
>> releases, and to have fine-grained control of exactly when and how
>> to upgrade it.
> The agreed version of MongoDB (currently 2.2.3) will be backported to
> precise and quantal; its still not in main so fixes right now would be
> driven through the Ubuntu server team (rather than from security team
> for example) - but they should be fixes, not upgrades :-).  I'm hoping
> that for 13.10 we can get mongodb into main so you get the full distro
> security support for this package (I really hate the embedded
> spidermonkey library but this is not the default in 2.4 so this is
> what I think is the trigger point for main inclusion).
>

What is the status on 2.2.3 in precise and quantal?  Right now we are 
thinking about adding it to the Juju PPA for those versions, and 
enabling that PPA (just for for state servers), so that for those using 
the ~juju PPA get a working Juju.

I think this will let us support those users (who will need a PPA 
anyway) in the short term, and buy us a little time to do this "the best 
way" when we have agreement there.

Is there anything we should be doing this week to make sure we're not 
painting ourselves in a corner?  James, what's your advice?

--Mark Ramm