Why is deb.nodesource.com installing 0.11 over 0.10?

[Alan Hoffmeister]

Hello everyone,

I just did an `apt-get upgrade` and node.js was upgraded from 0.10.35
to 0.11.15, but why? 0.11 isn't an unstable branch? I'm using the
nodesource repository on my Ubuntu 14.10.

Log:
Unpacking nodejs (0.11.15-1nodesource1~utopic1) over
(0.10.35-1nodesource1~utopic1) ...

--
Alan Hoffmeister
https://twitter.com/alan_hoff
https://github.com/alanhoff
https://keybase.io/alanhoff

[mscdex]

On Thursday, January 29, 2015 at 10:40:47 AM UTC-5, Alan Hoffmeister wrote:

I just did an `apt-get upgrade` and node.js was upgraded from 0.10.35
to 0.11.15, but why? 0.11 isn't an unstable branch? I'm using the
nodesource repository on my Ubuntu 14.10.

This is definitely an error since the `deb.nodesource.com/node` repo should contain only the latest stable version and I have verified that this repo is serving 0.11.15[1]. The `deb.nodesource.com/node-devel` is the repo that should contain the latest unstable version.

[1] https://deb.nodesource.com/node/dists/utopic/main/binary-amd64/Packages

[Peter Petrov]

On Thursday, January 29, 2015 at 8:10:47 PM UTC+2, mscdex wrote:

This is definitely an error since the `deb.nodesource.com/node` repo should contain only the latest stable version

Btw, even this is a bad idea. There should be separate channels for each branch - 0.10.x, 0.12.x (including 0.11.x), and so on. A package upgrade should never switch branches automatically, it must always be a human decision, otherwise this is unsuitable for use in production. Yes, one can try to use version pinning, but it's a poor and unnecessarily complicated solution.

[Dave Workman]

+1 just got bite by this. Doesn't happen on 14.04, but does on 14.10.

On Thursday, January 29, 2015 at 10:40:47 AM UTC-5, Alan Hoffmeister wrote: