Update mongodb to 2.2.0 (latest release)

[Troy Dawson]

On 10/09/2012 09:51 AM, Dennis Jacobfeuerborn wrote:
> On 10/08/2012 09:48 PM, Troy Dawson wrote:
>> On 10/05/2012 04:43 PM, Troy Dawson wrote:
>>> Hello,
>>> I have updated mongodb from 2.0.7 to 2.2.0.
>>> It is currently going through the normal channels for rawhide and Fedora 18.
>>>
>>> 10gen has a very good track record for being backwards compatible.
>>> According to their documentation "When upgrading a standalone mongod,
>>> 2.2 is a drop-in replacement." and "MongoDB 2.0 data files are
>>> compatible with 2.2-series binaries without any special migration process."
>>> If upgrading replica sets and sharded cluster, you should follow the
>>> procedures from their release notes.
>>> http://docs.mongodb.org/manual/release-notes/2.2/#upgrading
>>>
>>> What are people's thoughts on bringing it into Fedora 16, Fedora 17,
>>> EPEL6 and EPEL5?
>>>
>>> Troy Dawson
>>
>> I have had requests for mongodb 2.2.0 for Fedora 17, as well as EPEL 6
>> and 5.  I am going to build for those tomorrow and let things sit in
>> testing for at least a week (2 weeks for EPEL).
>>
>> The only concern I have received thus far is whether packages will need
>> to be rebuilt against the new mongodb 2.2.
>>
>> From everything I have looked at, the answer is no.
>> The API's should be backward compatible.
>> The libraries provided are the same name, there is no increase in number.
>>
>> $ rpm -qp --provides libmongodb-2.0.7-2.fc18.x86_64.rpm
>> libmongoclient.so()(64bit)
>> libmongodb = 2.0.7-2.fc18
>> libmongodb(x86-64) = 2.0.7-2.fc18
>>
>> $ rpm -qp --provides libmongodb-2.2.0-6.fc18.x86_64.rpm
>> libmongoclient.so()(64bit)
>> libmongodb = 2.2.0-6.fc18
>> libmongodb(x86-64) = 2.2.0-6.fc18
> 
> Updates to existing EPEL/Fedora version should probably wait until at least
> 2.2.1 is out. I've seen at least one report of sharding problems with 2.2.0
> that were confirmed by the developers and reported as fixed in trunk and to
> be released in 2.2.1.
> In general you should probably wait for at least one or two additional
> releases to catch the most blatant bugs in the new major version.
> 
> In as-of-yet unreleased verions like Fedora 18 this is not such a big issue
> since these will all be fresh setup and bugs will be noticed then and there
> but someone who is running 2.0 for a while in Fedora 17 or Centos 6 should
> not be hit by such things.
> 
> Regards,
>   Dennis
> 

Sorry, I did not see this before I sent my previous email.  What do you
think about building it for EPEL and just letting it sit in testing?  Or
do you think I should just hold off building it for EPEL completely
until 2.2.1 is out?

Troy