Re: [Pkg-javascript-devel] nodejs >= 6 for gitlab in stretch-backports

2018-05-10 Thread Pirate Praveen
On Thu, May 10, 2018 at 1:22 PM, Jérémy Lal wrote: Yes the server is setup by the tests. Anyway if local interface was not setup, you would have seen more test failures, so that was a bad suggestion. A better idea: this test might be depending on some libc-ares2 recent

Re: [Pkg-javascript-devel] nodejs >= 6 for gitlab in stretch-backports

2018-05-10 Thread Jérémy Lal
2018-05-10 9:15 GMT+02:00 Pirate Praveen : > > > On Thu, May 3, 2018 at 3:19 PM, Jérémy Lal wrote: > > > > 2018-05-03 11:32 GMT+02:00 Pirate Praveen : > >> >> >> On ബു, മേയ് 2, 2018 at 9:04 വൈകു, Jérémy Lal

Re: [Pkg-javascript-devel] nodejs >= 6 for gitlab in stretch-backports

2018-05-10 Thread Pirate Praveen
On Thu, May 3, 2018 at 3:19 PM, Jérémy Lal wrote: 2018-05-03 11:32 GMT+02:00 Pirate Praveen : On ബു, മേയ് 2, 2018 at 9:04 വൈകു, Jérémy Lal wrote: Correction: nodejs 8.11 supports both openssl 1.0.1 or openssl >= 1.1.0g.

Re: [Pkg-javascript-devel] nodejs >= 6 for gitlab in stretch-backports

2018-05-02 Thread Jérémy Lal
2018-05-02 13:44 GMT+02:00 Pirate Praveen : > Hi, > > I'd like to upload gitlab 10.6 to stretch-backports as backporting > security fixes is becoming difficult. My original idea was also > providing updates via backports, but gitlab switching to nodejs for > front end in

[Pkg-javascript-devel] nodejs >= 6 for gitlab in stretch-backports

2018-05-02 Thread Pirate Praveen
Hi, I'd like to upload gitlab 10.6 to stretch-backports as backporting security fixes is becoming difficult. My original idea was also providing updates via backports, but gitlab switching to nodejs for front end in gitlab 9 made that impossible. Now with all nodejs modules stuck in NEW for