[EPEL-devel] Re: nodejs update

2016-09-12 Thread Stephen Gallagher
On 09/08/2016 01:27 PM, Stephen Gallagher wrote: > On 08/22/2016 11:23 AM, Stephen Gallagher wrote: >> >> OK, as we stated before, we really need to get Node.js 6.x into the >> updates-testing repository soon. We mentioned that we wanted it to sit there >> for >> at least a month before we cut

[EPEL-devel] Re: nodejs update

2016-09-09 Thread Joe Orton
On Thu, Sep 08, 2016 at 01:27:54PM -0400, Stephen Gallagher wrote: > > * Node.js 4.x and 6.x both *strictly* require functionality from OpenSSL > > 1.0.2 > > and cannot run (or indeed build) against OpenSSL 1.0.1. Currently, both > > EPEL 6 > > and EPEL 7 have 1.0.1 in their buildroots. I am not

[EPEL-devel] Re: nodejs update

2016-09-08 Thread Rich Megginson
On 09/08/2016 11:27 AM, Stephen Gallagher wrote: On 08/22/2016 11:23 AM, Stephen Gallagher wrote: On 08/11/2016 07:43 AM, Stephen Gallagher wrote: On 08/11/2016 05:16 AM, Zuzana Svetlikova wrote: Hi! As some of you may know, nodejs package that is present in EPEL is pretty outdated. The

[EPEL-devel] Re: nodejs update

2016-09-08 Thread Stephen Gallagher
On 08/22/2016 11:23 AM, Stephen Gallagher wrote: > On 08/11/2016 07:43 AM, Stephen Gallagher wrote: >> On 08/11/2016 05:16 AM, Zuzana Svetlikova wrote: >>> Hi! >>> >>> As some of you may know, nodejs package that is present in >>> EPEL is pretty outdated. The current v0.10 that we have will >>> go

[EPEL-devel] Re: nodejs update

2016-08-25 Thread Rich Megginson
On 08/11/2016 05:43 AM, Stephen Gallagher wrote: On 08/11/2016 05:16 AM, Zuzana Svetlikova wrote: Hi! As some of you may know, nodejs package that is present in EPEL is pretty outdated. The current v0.10 that we have will go EOL in October and npm (package manager) is already not maintained.

[EPEL-devel] Re: nodejs update

2016-08-25 Thread Matthias Runge
On 23/08/16 03:48, Stephen Gallagher wrote: >> On Mon, Aug 22, 2016 at 4:23 PM, Stephen Gallagher >> > >> Let me (or open a rel-eng ticket) when you want a epel7-nodejs6 side >> tag to build it into. Will make it easier so you don't need to deal >> with a billion

[EPEL-devel] Re: nodejs update

2016-08-22 Thread Peter Robinson
On Mon, Aug 22, 2016 at 4:23 PM, Stephen Gallagher wrote: > On 08/11/2016 07:43 AM, Stephen Gallagher wrote: >> On 08/11/2016 05:16 AM, Zuzana Svetlikova wrote: >>> Hi! >>> >>> As some of you may know, nodejs package that is present in >>> EPEL is pretty outdated. The current

[EPEL-devel] Re: nodejs update

2016-08-12 Thread Stephen John Smoogen
at.com>, epel-devel-l...@redhat.com, > epel-de...@fedoraproject.org > Sent: Thursday, August 11, 2016 6:11:14 PM > Subject: Re: [EPEL-devel] Re: nodejs update > > On 11 August 2016 at 07:43, Stephen Gallagher <sgall...@redhat.com> wrote: > >>> tl;dr Need to upd

[EPEL-devel] Re: nodejs update

2016-08-12 Thread Zuzana Svetlikova
<epel-devel@lists.fedoraproject.org> Cc: "Zuzana Svetlikova" <zsvet...@redhat.com>, epel-devel-l...@redhat.com, epel-de...@fedoraproject.org Sent: Thursday, August 11, 2016 6:11:14 PM Subject: Re: [EPEL-devel] Re: nodejs update On 11 August 2016 at 07:43, Stephen Gallagher &l

[EPEL-devel] Re: nodejs update

2016-08-11 Thread Stephen John Smoogen
On 11 August 2016 at 07:43, Stephen Gallagher wrote: >> tl;dr Need to update nodejs, but can't decide if v4 or v6, >> v4: will update sooner, shorter support (2018-04-01) >> v6: longer support (2019-04-01), *might* break more things, >> won't be in stable sooner than

[EPEL-devel] Re: nodejs update

2016-08-11 Thread Stephen Gallagher
On 08/11/2016 05:16 AM, Zuzana Svetlikova wrote: > Hi! > > As some of you may know, nodejs package that is present in > EPEL is pretty outdated. The current v0.10 that we have will > go EOL in October and npm (package manager) is already not > maintained. > > Currently, upstreams' plan is to