Bug#748490: Ping? Any update on mongodb 2.6 packaging?

[Apollon Oikonomopoulos]

Hi all,

As far as the MongoDB 2.4 to 2.6 transition goes, it is supported 
upstream[1] as a "binary-compatible “drop-in” upgrade" and 
application-side compatibility can be checked in advance by running
db.upgradeCheckAllDBs() on a 2.6 client connected to the 2.4 server. In 
that respect, the transition is far less of a problem than the 
2.0-to-2.4 transition needed for a Wheezy to Jessie upgrade. That said, 
I'm in favor of uploading 2.6 to unstable using the mongodb source name 
(and not mongodb-2.6) and then providing a Jessie backport.

Since we are in the process of upgrading to MongoDB 2.6 at work, I've 
rolled out a 2.6.11 package, trying to benefit from the changes done 
both in Ubuntu and László's updated package. For anyone interested, the 
source (signed with my DD key) is at

  https://dmesg.gr/packages/mongodb_2.6.11-0.1.dsc

I've cleaned up the patches, and done some packaging overhaul, including 
making hardened buildflags work. The changelog since 2.4.14-3 lists 
every change done, although some attribution may be missing (apologies 
for that). I've already tested the clients on our infrastructure, and we 
will start rolling out the server package soon on Jessie.

Regards,
Apollon

[1] https://docs.mongodb.org/manual/release-notes/2.6-upgrade/


signature.asc
Description: PGP signature

Bug#748490: Ping? Any update on mongodb 2.6 packaging?

[GCS]

Hi,

On Mon, Jan 18, 2016 at 1:29 PM, Apollon Oikonomopoulos
 wrote:
> As far as the MongoDB 2.4 to 2.6 transition goes, it is supported
> upstream[1] as a "binary-compatible “drop-in” upgrade" and
> application-side compatibility can be checked in advance by running
> db.upgradeCheckAllDBs() on a 2.6 client connected to the 2.4 server. In
> that respect, the transition is far less of a problem than the
> 2.0-to-2.4 transition needed for a Wheezy to Jessie upgrade. That said,
> I'm in favor of uploading 2.6 to unstable using the mongodb source name
> (and not mongodb-2.6) and then providing a Jessie backport.
 The Wheezy -> Jessie path missed the 2.2 version and providing
mongodb-version package names helps to avoid this.
But sure, let the names remain as-is.

> Since we are in the process of upgrading to MongoDB 2.6 at work, I've
> rolled out a 2.6.11 package, trying to benefit from the changes done
> both in Ubuntu and László's updated package.
 May you share your experience? Any manual interaction was needed?

> I've already tested the clients on our infrastructure, and we
> will start rolling out the server package soon on Jessie.
 Please keep us posted.

Thanks,
Laszlo/GCS

Bug#748490: Ping? Any update on mongodb 2.6 packaging?

[Apollon Oikonomopoulos]

On 15:09 Mon 18 Jan , László Böszörményi wrote:
> Hi,
> 
> On Mon, Jan 18, 2016 at 1:29 PM, Apollon Oikonomopoulos
>  wrote:
> > As far as the MongoDB 2.4 to 2.6 transition goes, it is supported
> > upstream[1] as a "binary-compatible “drop-in” upgrade" and
> > application-side compatibility can be checked in advance by running
> > db.upgradeCheckAllDBs() on a 2.6 client connected to the 2.4 server. In
> > that respect, the transition is far less of a problem than the
> > 2.0-to-2.4 transition needed for a Wheezy to Jessie upgrade. That said,
> > I'm in favor of uploading 2.6 to unstable using the mongodb source name
> > (and not mongodb-2.6) and then providing a Jessie backport.
>  The Wheezy -> Jessie path missed the 2.2 version and providing
> mongodb-version package names helps to avoid this.
> But sure, let the names remain as-is.

Unfortunately, there seems to be no easy solution for this problem.  
Since upstream only supports transitions between consecutive stable 
releases, Debian should really provide packages for all intermediate 
versions to facilitate upgrades. But yes, in the Wheezy -> Jessie case, 
using a different package name (although not source name), would at 
least guarantee that no automatic upgrades would take place.

> 
> > Since we are in the process of upgrading to MongoDB 2.6 at work, I've
> > rolled out a 2.6.11 package, trying to benefit from the changes done
> > both in Ubuntu and László's updated package.
>  May you share your experience? Any manual interaction was needed?

Sofar I've run db.upgradeCheckAllDBs() against one of our clusters with 
a 500 GB dataset and tens of millions of documents. All-in-all it 
emitted errors regarding mostly dots in field names (which has been a 
restriction since at least 2.2) and just 4 (!) key-too-long documents.  
I've seen RDBMS migrations that are much worse than this, plus at least 
now we can get a glimpse of what we should fix *before* actually 
upgrading the server :).

> > I've already tested the clients on our infrastructure, and we
> > will start rolling out the server package soon on Jessie.
>  Please keep us posted.

We will soon upgrade our development instances, so I will let you know.

Regards,
Apollon

Bug#748490: Ping? Any update on mongodb 2.6 packaging?

[Matijs van Zuijlen]

Hi László,

On 07/10/15 11:12, Matijs van Zuijlen wrote:
> On 07/10/15 11:08, László Böszörményi (GCS) wrote:
>> Hi all,
>>
>> On Sat, Oct 3, 2015 at 4:21 PM, László Böszörményi (GCS)  
>> wrote:
>>> On Fri, Oct 2, 2015 at 9:20 PM, David I. Lehn  wrote:
 It's been a couple weeks, any chance you could upload what you have to
 experimental?
>>>  I still couldn't test it but sure I do make it public[1] for others
>>> that may help with testing.
>> [...]
>>> [1] dget -x http://www.barcikacomp.hu/gcs/mongodb-2.6_2.6.11-1.dsc
>>  Just a friendly ping, any of you still interested in helping to test
>> the package? Should I wait more for feedback?
>>
>> Kind regards,
>> Laszlo/GCS
>>
> 
> Hi Laszlo,
> 
> I can take a look at this package this weekend. Thanks for making it public!

Taking a look took a little longer because compiling took a large part of sunday
afternoon :-).

I was able to install the resulting packages succesfully, except the 'mongodb'
package, which seems to need an epoch in its version number. Without it, it
conflicts with libstdc++6 version 5.2.1-22, which Breaks: mongodb <= 1:2.4.14-2.

I ran the unit tests for errbit (http://errbit.github.io/errbit/), which is the
application I use mongodb with, and they all passed. The latest errbit version
requires mongodb 2.6.

If there is anything else you would like me to check or any tests I should run,
please let me know.

Regards,
-- 
Matijs



signature.asc
Description: OpenPGP digital signature

Bug#748490: Ping? Any update on mongodb 2.6 packaging?

[Matijs van Zuijlen]

On 07/10/15 11:08, László Böszörményi (GCS) wrote:
> Hi all,
> 
> On Sat, Oct 3, 2015 at 4:21 PM, László Böszörményi (GCS)  
> wrote:
>> On Fri, Oct 2, 2015 at 9:20 PM, David I. Lehn  wrote:
>>> It's been a couple weeks, any chance you could upload what you have to
>>> experimental?
>>  I still couldn't test it but sure I do make it public[1] for others
>> that may help with testing.
> [...]
>> [1] dget -x http://www.barcikacomp.hu/gcs/mongodb-2.6_2.6.11-1.dsc
>  Just a friendly ping, any of you still interested in helping to test
> the package? Should I wait more for feedback?
> 
> Kind regards,
> Laszlo/GCS
> 

Hi Laszlo,

I can take a look at this package this weekend. Thanks for making it public!

Regards,
-- 
Matijs



signature.asc
Description: OpenPGP digital signature

Bug#748490: Ping? Any update on mongodb 2.6 packaging?

[GCS]

Hi all,

On Sat, Oct 3, 2015 at 4:21 PM, László Böszörményi (GCS)  
wrote:
> On Fri, Oct 2, 2015 at 9:20 PM, David I. Lehn  wrote:
>> It's been a couple weeks, any chance you could upload what you have to
>> experimental?
>  I still couldn't test it but sure I do make it public[1] for others
> that may help with testing.
[...]
> [1] dget -x http://www.barcikacomp.hu/gcs/mongodb-2.6_2.6.11-1.dsc
 Just a friendly ping, any of you still interested in helping to test
the package? Should I wait more for feedback?

Kind regards,
Laszlo/GCS

Bug#748490: Ping? Any update on mongodb 2.6 packaging?

[GCS]

On Fri, Oct 2, 2015 at 9:20 PM, David I. Lehn  wrote:
> On Tue, 15 Sep 2015 10:49:52 +
> =?UTF-8?B?TMOhc3psw7MgQsO2c3rDtnJtw6lueWkgKEdDUyk=?= 
> wrote:
>>  I've a package ready, needs some testing. Will upload in the coming days.
>>
>
> It's been a couple weeks, any chance you could upload what you have to
> experimental?
 I still couldn't test it but sure I do make it public[1] for others
that may help with testing. First please report back if you can
compile it on other architectures than amd64 where it does on my box.
Warning, please don't put this into your production systems yet.
Note I changed the binary package names to end with -2.6 as I will
need to support several versions for the Stretch release.

Thanks in advance,
Laszlo/GCS
[1] dget -x http://www.barcikacomp.hu/gcs/mongodb-2.6_2.6.11-1.dsc

Bug#748490: Ping? Any update on mongodb 2.6 packaging?

[David I. Lehn]

On Tue, 15 Sep 2015 10:49:52 +
=?UTF-8?B?TMOhc3psw7MgQsO2c3rDtnJtw6lueWkgKEdDUyk=?= 
wrote:
> On Tue, Sep 15, 2015 at 8:44 AM, Thomas Goirand  wrote:
> > Any update on this bug? It's been since June that James Page asked for a
> > new version in Experimental, with no reply from your side. Do you have
> > time to work on it?
>  I've a package ready, needs some testing. Will upload in the coming days.
>

It's been a couple weeks, any chance you could upload what you have to
experimental?

-dave

Bug#748490: Ping? Any update on mongodb 2.6 packaging?

[Thomas Goirand]

Hi Laszlo,

Any update on this bug? It's been since June that James Page asked for a
new version in Experimental, with no reply from your side. Do you have
time to work on it? Would you accept contribution to this packaging (in
the form of an NMU or some git push?)?

Cheers,

Thomas Goirand (zigo)

Bug#748490: Ping? Any update on mongodb 2.6 packaging?

[GCS]

Hi zigo,

On Tue, Sep 15, 2015 at 8:44 AM, Thomas Goirand  wrote:
> Any update on this bug? It's been since June that James Page asked for a
> new version in Experimental, with no reply from your side. Do you have
> time to work on it?
 I've a package ready, needs some testing. Will upload in the coming days.

Laszlo/GCS