FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Redhat > Fedora Development

 
 
LinkBack Thread Tools
 
Old 10-05-2012, 09:43 PM
Troy Dawson
 
Default Update mongodb to 2.2.0 (latest release)

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
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
 
Old 10-08-2012, 07:48 PM
Troy Dawson
 
Default Update mongodb to 2.2.0 (latest release)

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

Thank You
Troy Dawson

--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
 
Old 10-08-2012, 07:53 PM
Michał Piotrowski
 
Default Update mongodb to 2.2.0 (latest release)

Hi,

2012/10/8 Troy Dawson <tdawson@redhat.com>:
> 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).

I'll test on Fedora 17 and I'll let you know if I will have problems.

>
> 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
>
> Thank You
> Troy Dawson
>
> --
> devel mailing list
> devel@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel



--
Best regards,
Michal

http://eventhorizon.pl/
https://getactive.pl/
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
 
Old 10-08-2012, 08:27 PM
Dan Horák
 
Default Update mongodb to 2.2.0 (latest release)

Troy Dawson p*še v Po 08. 10. 2012 v 14:48 -0500:
> 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.

you can use the abi-compliance-checker tool to confirm that


Dan


--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
 
Old 10-09-2012, 11:23 AM
Andrey Ponomarenko
 
Default Update mongodb to 2.2.0 (latest release)

Dan Horák wrote:

Troy Dawson p*še v Po 08. 10. 2012 v 14:48 -0500:

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.

you can use the abi-compliance-checker tool to confirm that


or look at the upstream-tracker report for mongodb:
http://upstream-tracker.org/versions/mongodb.html


particularly, the compatibility report between 2.0.7 and 2.2.0 versions
is:
http://upstream-tracker.org/compat_reports/mongodb/2.0.7_to_2.2.0/compat_report.html


--
Andrey Ponomarenko, ROSA Lab.

--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
 
Old 10-09-2012, 02:51 PM
Dennis Jacobfeuerborn
 
Default Update mongodb to 2.2.0 (latest release)

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

--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
 
Old 10-09-2012, 02:52 PM
Troy Dawson
 
Default Update mongodb to 2.2.0 (latest release)

On 10/09/2012 06:23 AM, Andrey Ponomarenko wrote:
> Dan Horák wrote:
>> Troy Dawson p*še v Po 08. 10. 2012 v 14:48 -0500:
>>> 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.
>> you can use the abi-compliance-checker tool to confirm that
>
> or look at the upstream-tracker report for mongodb:
> http://upstream-tracker.org/versions/mongodb.html
>
> particularly, the compatibility report between 2.0.7 and 2.2.0 versions
> is:
> http://upstream-tracker.org/compat_reports/mongodb/2.0.7_to_2.2.0/compat_report.html
>
>

Well, that isn't encouraging.
I'm pretty sure at the very least we need to update the various mongo
drivers (rubygem-mongo, pymongo, etc..)
I'm still going to build mongodb 2.2.0 for the various releases,
otherwise people won't be able to test it. But they may sit in testing
for longer than the standard time.

Troy

--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
 
Old 10-09-2012, 03:18 PM
Troy Dawson
 
Default Update mongodb to 2.2.0 (latest release)

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

--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
 
Old 10-09-2012, 04:55 PM
Pete Zaitcev
 
Default Update mongodb to 2.2.0 (latest release)

On Tue, 09 Oct 2012 09:52:04 -0500
Troy Dawson <tdawson@redhat.com> wrote:

> I'm pretty sure at the very least we need to update the various mongo
> drivers (rubygem-mongo, pymongo, etc..)

Well, I suppose can rebuild iwhd in F17 and bump Requires: mongo >= 2.2.
Not ideal in a stable release, but it you think it's ok...

I see Nate is AWOL in this thread suspiciously.

-- Pete
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
 
Old 10-15-2012, 02:38 PM
Troy Dawson
 
Default Update mongodb to 2.2.0 (latest release)

On 10/09/2012 10:18 AM, Troy Dawson wrote:
> 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
>

mongodb 2.2.0 is in updates-testing for Fedora 17, and epel-testing for
EPEL 6.
Due to concerns about updating from 2.0.x to 2.2.x these will probably
remain in testing until 2.2.1 is out and packaged.
So, if you are running Fedora 17, or EPEL 6, you can test mongodb 2.2 by
using the testing repositories. But it won't go into those main repo's
until at least mongo 2.2.1.
Thank you for the feedback I've received.
Troy
p.s. Nick has been working with me some off-line. But since my project
needed 2.2, and his didn't, I took the lead for this.

--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
 

Thread Tools




All times are GMT. The time now is 02:11 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org