Re: [Pkg-javascript-devel] nodejs-12 transition

[Jérémy Lal]

Le sam. 20 juin 2020 à 19:42,  a écrit :

> > Le lun. 1 juin 2020 à 07:24, Xavier  > >
> >  a écrit :
> >
> > > >* Le 31/05/2020 à 18:04, Nilesh Patra a écrit :
> *> >* > It doesn't go well !
> *> >* > Both mips archs won't compile,
> *> >* >
> *> >* >
> *> >* > Is it only mips that this fails on?
> *> >* > If yes, maybe this can be ignored for the moment.
> *> >> >* No we can't: testing migration requires success on amd64, arm64, 
> armel,
> *> >* armhf, i386, mips64el, mipsel, ppc64el and s390x. Only other arch are
> *> >* optional.
> *> >> >* Seconded, unless upstream v8 reallly drop support for some mips 
> archs.
> *> Also i forgot to mention "icu 67 is still in experimental".
> >
> > Jérémy
>
>
> Happy to see the successful build of nodejs now, 
> https://buildd.debian.org/status/package.php?p=nodejs
>
> What remains left before this can be sent to testing ?
>

I have the feeling a good solution is yet to be found for
https://bugs.debian.org/963039

Jérémy
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] nodejs-12 transition

[Jérémy Lal]

Is failure of node-srs (which is not in testing, btw) preventing auto
transition ?

Jérémy
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] nodejs-12 transition

[Jonas Smedegaard]

Quoting Jérémy Lal (2020-06-12 18:12:15)
> Le lun. 8 juin 2020 à 11:13, Jonas Smedegaard  a écrit :
> 
> > Quoting Jonas Smedegaard (2020-05-25 12:09:53)
> > > Quoting Jérémy Lal (2020-05-25 10:51:32)
> > > > [nodejs 12 is] ready to be built, but not ready to go in testing:
> > > >
> > https://buildd.debian.org/status/package.php?p=nodejs=experimental
> > > >
> > > > - amd64 some tests won't pass because of network issues
> > > >   I never figured why some build servers fail on this, and some not.
> > > > *  If anyone knows an explanation, that'll help.*
> > >
> > > I suggest to ask on debian-devel@l.d.o
> > >
> > > Alternatively - if those tests are possible to identify and isolate -
> > > skip them during build and have them run at autobuildtest instead.
> >
> > Not sure if you're already made aware, but nodejs was mentioned today in
> > a perl bug where (as I understand it) the suspicion is that failures
> > connecting to localhost is related to systems having both ipv4 127.0.0.1
> > and ipv6 ::1.
> >
> > See bug#962318.
> >
> 
> That was an helpful hint.
> I made a bad fix for nodejs 12 to be able to build on conova at the moment,
> and upstream nodejs/libuv has respawned the discussion around this issue,
> as i figured out they were already well aware of it.
> 
> On another front, i realized /usr/include/nodejs was bad because of two
> things:
> - upstream expects /usr/include/node, if any
> - upstream now has a "correct" set of headers to install there
> So, from now on nodejs 12 installs headers like that.
> But i didn't want to hinder the transition, so i left the old way in
> /usr/include/nodejs,
> and i'll change node-gyp to use /usr/include/node when all is in testing.

Great work!

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] nodejs-12 transition

[Jérémy Lal]

Le lun. 8 juin 2020 à 11:13, Jonas Smedegaard  a écrit :

> Quoting Jonas Smedegaard (2020-05-25 12:09:53)
> > Quoting Jérémy Lal (2020-05-25 10:51:32)
> > > [nodejs 12 is] ready to be built, but not ready to go in testing:
> > >
> https://buildd.debian.org/status/package.php?p=nodejs=experimental
> > >
> > > - amd64 some tests won't pass because of network issues
> > >   I never figured why some build servers fail on this, and some not.
> > > *  If anyone knows an explanation, that'll help.*
> >
> > I suggest to ask on debian-devel@l.d.o
> >
> > Alternatively - if those tests are possible to identify and isolate -
> > skip them during build and have them run at autobuildtest instead.
>
> Not sure if you're already made aware, but nodejs was mentioned today in
> a perl bug where (as I understand it) the suspicion is that failures
> connecting to localhost is related to systems having both ipv4 127.0.0.1
> and ipv6 ::1.
>
> See bug#962318.
>

That was an helpful hint.
I made a bad fix for nodejs 12 to be able to build on conova at the moment,
and upstream nodejs/libuv has respawned the discussion around this issue,
as i figured out they were already well aware of it.

On another front, i realized /usr/include/nodejs was bad because of two
things:
- upstream expects /usr/include/node, if any
- upstream now has a "correct" set of headers to install there
So, from now on nodejs 12 installs headers like that.
But i didn't want to hinder the transition, so i left the old way in
/usr/include/nodejs,
and i'll change node-gyp to use /usr/include/node when all is in testing.

Jérémy
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] nodejs-12 transition

[Jonas Smedegaard]

Quoting Jonas Smedegaard (2020-05-25 12:09:53)
> Quoting Jérémy Lal (2020-05-25 10:51:32)
> > [nodejs 12 is] ready to be built, but not ready to go in testing:
> > https://buildd.debian.org/status/package.php?p=nodejs=experimental
> > 
> > - amd64 some tests won't pass because of network issues
> >   I never figured why some build servers fail on this, and some not.
> > *  If anyone knows an explanation, that'll help.*
> 
> I suggest to ask on debian-devel@l.d.o
> 
> Alternatively - if those tests are possible to identify and isolate - 
> skip them during build and have them run at autobuildtest instead.

Not sure if you're already made aware, but nodejs was mentioned today in 
a perl bug where (as I understand it) the suspicion is that failures 
connecting to localhost is related to systems having both ipv4 127.0.0.1 
and ipv6 ::1.

See bug#962318.

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] nodejs-12 transition

[Jérémy Lal]

Le lun. 1 juin 2020 à 07:24, Xavier  a écrit :

> Le 31/05/2020 à 18:04, Nilesh Patra a écrit :
> > It doesn't go well !
> > Both mips archs won't compile,
> >
> >
> > Is it only mips that this fails on?
> > If yes, maybe this can be ignored for the moment.
>
> No we can't: testing migration requires success on amd64, arm64, armel,
> armhf, i386, mips64el, mipsel, ppc64el and s390x. Only other arch are
> optional.
>
> Seconded, unless upstream v8 reallly drop support for some mips archs.
Also i forgot to mention "icu 67 is still in experimental".

Jérémy
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] nodejs-12 transition

[Xavier]

Le 31/05/2020 à 18:04, Nilesh Patra a écrit :
> It doesn't go well !
> Both mips archs won't compile, 
> 
> 
> Is it only mips that this fails on?
> If yes, maybe this can be ignored for the moment.

No we can't: testing migration requires success on amd64, arm64, armel,
armhf, i386, mips64el, mipsel, ppc64el and s390x. Only other arch are
optional.

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] nodejs-12 transition

[Nilesh Patra]

>
> It doesn't go well !
> Both mips archs won't compile,
>

Is it only mips that this fails on?
If yes, maybe this can be ignored for the moment.

and i'm checking if this v8 upstream commit helps:
> https://chromium-review.googlesource.com/c/v8/v8/+/2153187
>
> Besides that, -g1 and --max-parallel are coming.
> (My first attempt was completely wrong).
>

Thanks for all your help and work on this.
Really appreciate it.

Kinds regards,
Nilesh
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] nodejs-12 transition

[Jérémy Lal]

Le ven. 29 mai 2020 à 23:13, Jérémy Lal  a écrit :

>
>
> Le ven. 29 mai 2020 à 23:08, Nilesh Patra  a écrit :
>
>> Hi Jérémy
>>
>> On Fri, 29 May 2020, 23:47 Jérémy Lal,  wrote:
>>
>>>
>>>
>>> Le lun. 25 mai 2020 à 12:10, Jonas Smedegaard  a écrit :
>>>
 Quoting Jérémy Lal (2020-05-25 10:51:32)
 > [nodejs 12 is] ready to be built, but not ready to go in testing:
 >
 https://buildd.debian.org/status/package.php?p=nodejs=experimental
 >
 > - amd64 some tests won't pass because of network issues
 >   I never figured why some build servers fail on this, and some not.
 > *  If anyone knows an explanation, that'll help.*

 I suggest to ask on debian-devel@l.d.o

 Alternatively - if those tests are possible to identify and isolate -
 skip them during build and have them run at autobuildtest instead.


 > - armhf, i386: dh_dwz fails because it exhausts memory.
 >   Somewhat fixed by ignoring those failures. *Is there a better
 option ?*

 Maybe this (used e.g. in modero package) helps:

 # reduce debugging information on 32bit archs
 # to avoid some FTBFS (memory axhaustion of build environment?)
 ifeq ($(DEB_HOST_ARCH_BITS),32)
 export DEB_CXXFLAGS_MAINT_APPEND = -g1
 endif


>>> Good idea ! I'm going to try that now.
>>>
>>>
>>>
 > - mipsel: fails to build, OOM as some point.
 >   That was on a 8GB memory machine, so i suppose it's bad luck,
 something
 >   else was using memory maybe.

 Might be helped from above as well.

 Might also help to disable parallel builds for that architecture.

>>>
>>> Yes, indeed, going to do that too, if that's not already the case.
>>>
>>
>> With the latest upload to experimental
>> Looks like you managed to fix all(most of) the stuff. Yay! :-)
>> Is this ready now to migrate?
>>
>
>
> Let's see how it goes...
>

It doesn't go well !
Both mips archs won't compile, and i'm checking if this v8 upstream commit
helps:
https://chromium-review.googlesource.com/c/v8/v8/+/2153187

Besides that, -g1 and --max-parallel are coming.
(My first attempt was completely wrong).

Jérémy
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] nodejs-12 transition

[Jérémy Lal]

Le ven. 29 mai 2020 à 23:08, Nilesh Patra  a écrit :

> Hi Jérémy
>
> On Fri, 29 May 2020, 23:47 Jérémy Lal,  wrote:
>
>>
>>
>> Le lun. 25 mai 2020 à 12:10, Jonas Smedegaard  a écrit :
>>
>>> Quoting Jérémy Lal (2020-05-25 10:51:32)
>>> > [nodejs 12 is] ready to be built, but not ready to go in testing:
>>> >
>>> https://buildd.debian.org/status/package.php?p=nodejs=experimental
>>> >
>>> > - amd64 some tests won't pass because of network issues
>>> >   I never figured why some build servers fail on this, and some not.
>>> > *  If anyone knows an explanation, that'll help.*
>>>
>>> I suggest to ask on debian-devel@l.d.o
>>>
>>> Alternatively - if those tests are possible to identify and isolate -
>>> skip them during build and have them run at autobuildtest instead.
>>>
>>>
>>> > - armhf, i386: dh_dwz fails because it exhausts memory.
>>> >   Somewhat fixed by ignoring those failures. *Is there a better option
>>> ?*
>>>
>>> Maybe this (used e.g. in modero package) helps:
>>>
>>> # reduce debugging information on 32bit archs
>>> # to avoid some FTBFS (memory axhaustion of build environment?)
>>> ifeq ($(DEB_HOST_ARCH_BITS),32)
>>> export DEB_CXXFLAGS_MAINT_APPEND = -g1
>>> endif
>>>
>>>
>> Good idea ! I'm going to try that now.
>>
>>
>>
>>> > - mipsel: fails to build, OOM as some point.
>>> >   That was on a 8GB memory machine, so i suppose it's bad luck,
>>> something
>>> >   else was using memory maybe.
>>>
>>> Might be helped from above as well.
>>>
>>> Might also help to disable parallel builds for that architecture.
>>>
>>
>> Yes, indeed, going to do that too, if that's not already the case.
>>
>
> With the latest upload to experimental
> Looks like you managed to fix all(most of) the stuff. Yay! :-)
> Is this ready now to migrate?
>


Let's see how it goes...
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] nodejs-12 transition

[Nilesh Patra]

Hi Jérémy

On Fri, 29 May 2020, 23:47 Jérémy Lal,  wrote:

>
>
> Le lun. 25 mai 2020 à 12:10, Jonas Smedegaard  a écrit :
>
>> Quoting Jérémy Lal (2020-05-25 10:51:32)
>> > [nodejs 12 is] ready to be built, but not ready to go in testing:
>> >
>> https://buildd.debian.org/status/package.php?p=nodejs=experimental
>> >
>> > - amd64 some tests won't pass because of network issues
>> >   I never figured why some build servers fail on this, and some not.
>> > *  If anyone knows an explanation, that'll help.*
>>
>> I suggest to ask on debian-devel@l.d.o
>>
>> Alternatively - if those tests are possible to identify and isolate -
>> skip them during build and have them run at autobuildtest instead.
>>
>>
>> > - armhf, i386: dh_dwz fails because it exhausts memory.
>> >   Somewhat fixed by ignoring those failures. *Is there a better option
>> ?*
>>
>> Maybe this (used e.g. in modero package) helps:
>>
>> # reduce debugging information on 32bit archs
>> # to avoid some FTBFS (memory axhaustion of build environment?)
>> ifeq ($(DEB_HOST_ARCH_BITS),32)
>> export DEB_CXXFLAGS_MAINT_APPEND = -g1
>> endif
>>
>>
> Good idea ! I'm going to try that now.
>
>
>
>> > - mipsel: fails to build, OOM as some point.
>> >   That was on a 8GB memory machine, so i suppose it's bad luck,
>> something
>> >   else was using memory maybe.
>>
>> Might be helped from above as well.
>>
>> Might also help to disable parallel builds for that architecture.
>>
>
> Yes, indeed, going to do that too, if that's not already the case.
>

With the latest upload to experimental
Looks like you managed to fix all(most of) the stuff. Yay! :-)
Is this ready now to migrate?

Kind regards,
Nilesh
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] nodejs-12 transition

[Xavier]

Le 25/05/2020 à 11:42, Jérémy Lal a écrit :
> 
> 
> Le lun. 25 mai 2020 à 11:34, Xavier  > a écrit :
> 
> Le 25/05/2020 à 10:51, Jérémy Lal a écrit :
> >
> >
> > Le lun. 25 mai 2020 à 09:22, Nilesh Patra  
> > >> a écrit :
> >
> >     Hi Jérémy
> >
> >     On Sat, 7 Mar 2020, 14:34 Jérémy Lal,  
> >     >> wrote:
> >
> >
> >
> >         Le sam. 7 mars 2020 à 06:18, Nilesh Patra
> mailto:npatra...@gmail.com>
> >         >>
> a écrit :
> >
> >
> >
> >                 I think we should start Node.js 12 migration (with
> >                 rollup, webpack,
> >                 gulp,...), this will also fix some RC/FTBFS bugs,
> should we?
> >                 I fixed a lot of failing autopkgtest errors (using [1]
> >                 list), most of
> >                 the remaining packages in this list will be fixed by
> >                 node-iconv rebuild.
> >
> >
> >             Agreed. Node-nodedbi is removed from testing, officially
> >             now. We can file a (RC) bug against Node-srs for it to
> _not_
> >             migrate, same for Node-millstone.
> >             Nodejs transition is also required for acorn transition,
> >             from what I read on the mailing list.
> >
> >             As it's been pending now, for a long time and there's not
> >             much to be done except fixing these last 2-3 blockers,
> which
> >             will be removed (from testing) anyway.
> >             Would it be a good time to start the transition?
> >             If yes, It would be great to start in other
> transitions, :)
> >
> >
> >
> >         Right now node is waiting upon icu >=  64, which won't be
> in sid
> >         before ~may.
> >
> >
> >     This is probably the time now - may ends with the coming weekend.
> >     Any updates if this is in sid or when this would get to sid if it
> >     isn't already?
> >
> >
> > It's ready to be built, but not ready to go in testing:
> >
> https://buildd.debian.org/status/package.php?p=nodejs=experimental
> >
> > - amd64 some tests won't pass because of network issues
> >   I never figured why some build servers fail on this, and some not.
> > *  If anyone knows an explanation, that'll help.*
> > - armhf, i386: dh_dwz fails because it exhausts memory.
> >   Somewhat fixed by ignoring those failures. *Is there a better
> option ?*
> > - mips64el: tools/test.py no longer recognize the arch (it should
> get it
> > from
> >   the one mapped in debian/rules). Easy to fix.
> > - mipsel: fails to build, OOM as some point.
> >   That was on a 8GB memory machine, so i suppose it's bad luck,
> something
> >   else was using memory maybe.
> >
> > Jérémy
> 
> Hi,
> 
> there is a new "needs-internet" restriction in autopkgtest, maybe this
> will fix one pb
> 
> 
> Indeed, but no: it happens during the build phase.
> (that way we can get architecture-related test failures).
> 
> Also the tests are not requiring internet access, they only tcp/udp,
> ipv4/6 on localhost.

nodejs 12 is required at least to fix node-hoek* problems


-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] nodejs-12 transition

[Jonas Smedegaard]

Quoting Jérémy Lal (2020-05-25 10:51:32)
> [nodejs 12 is] ready to be built, but not ready to go in testing:
> https://buildd.debian.org/status/package.php?p=nodejs=experimental
> 
> - amd64 some tests won't pass because of network issues
>   I never figured why some build servers fail on this, and some not.
> *  If anyone knows an explanation, that'll help.*

I suggest to ask on debian-devel@l.d.o

Alternatively - if those tests are possible to identify and isolate - 
skip them during build and have them run at autobuildtest instead.


> - armhf, i386: dh_dwz fails because it exhausts memory.
>   Somewhat fixed by ignoring those failures. *Is there a better option ?*

Maybe this (used e.g. in modero package) helps:

# reduce debugging information on 32bit archs
# to avoid some FTBFS (memory axhaustion of build environment?)
ifeq ($(DEB_HOST_ARCH_BITS),32)
export DEB_CXXFLAGS_MAINT_APPEND = -g1
endif



> - mipsel: fails to build, OOM as some point.
>   That was on a 8GB memory machine, so i suppose it's bad luck, something
>   else was using memory maybe.

Might be helped from above as well.

Might also help to disable parallel builds for that architecture.


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] nodejs-12 transition

[Jérémy Lal]

Le lun. 25 mai 2020 à 11:34, Xavier  a écrit :

> Le 25/05/2020 à 10:51, Jérémy Lal a écrit :
> >
> >
> > Le lun. 25 mai 2020 à 09:22, Nilesh Patra  > > a écrit :
> >
> > Hi Jérémy
> >
> > On Sat, 7 Mar 2020, 14:34 Jérémy Lal,  > > wrote:
> >
> >
> >
> > Le sam. 7 mars 2020 à 06:18, Nilesh Patra  > > a écrit :
> >
> >
> >
> > I think we should start Node.js 12 migration (with
> > rollup, webpack,
> > gulp,...), this will also fix some RC/FTBFS bugs, should
> we?
> > I fixed a lot of failing autopkgtest errors (using [1]
> > list), most of
> > the remaining packages in this list will be fixed by
> > node-iconv rebuild.
> >
> >
> > Agreed. Node-nodedbi is removed from testing, officially
> > now. We can file a (RC) bug against Node-srs for it to _not_
> > migrate, same for Node-millstone.
> > Nodejs transition is also required for acorn transition,
> > from what I read on the mailing list.
> >
> > As it's been pending now, for a long time and there's not
> > much to be done except fixing these last 2-3 blockers, which
> > will be removed (from testing) anyway.
> > Would it be a good time to start the transition?
> > If yes, It would be great to start in other transitions, :)
> >
> >
> >
> > Right now node is waiting upon icu >=  64, which won't be in sid
> > before ~may.
> >
> >
> > This is probably the time now - may ends with the coming weekend.
> > Any updates if this is in sid or when this would get to sid if it
> > isn't already?
> >
> >
> > It's ready to be built, but not ready to go in testing:
> > https://buildd.debian.org/status/package.php?p=nodejs=experimental
> >
> > - amd64 some tests won't pass because of network issues
> >   I never figured why some build servers fail on this, and some not.
> > *  If anyone knows an explanation, that'll help.*
> > - armhf, i386: dh_dwz fails because it exhausts memory.
> >   Somewhat fixed by ignoring those failures. *Is there a better option ?*
> > - mips64el: tools/test.py no longer recognize the arch (it should get it
> > from
> >   the one mapped in debian/rules). Easy to fix.
> > - mipsel: fails to build, OOM as some point.
> >   That was on a 8GB memory machine, so i suppose it's bad luck, something
> >   else was using memory maybe.
> >
> > Jérémy
>
> Hi,
>
> there is a new "needs-internet" restriction in autopkgtest, maybe this
> will fix one pb
>

Indeed, but no: it happens during the build phase.
(that way we can get architecture-related test failures).

Also the tests are not requiring internet access, they only tcp/udp, ipv4/6
on localhost.
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] nodejs-12 transition

[Xavier]

Le 25/05/2020 à 10:51, Jérémy Lal a écrit :
> 
> 
> Le lun. 25 mai 2020 à 09:22, Nilesh Patra  > a écrit :
> 
> Hi Jérémy
> 
> On Sat, 7 Mar 2020, 14:34 Jérémy Lal,  > wrote:
> 
> 
> 
> Le sam. 7 mars 2020 à 06:18, Nilesh Patra  > a écrit :
> 
> 
> 
> I think we should start Node.js 12 migration (with
> rollup, webpack,
> gulp,...), this will also fix some RC/FTBFS bugs, should we?
> I fixed a lot of failing autopkgtest errors (using [1]
> list), most of
> the remaining packages in this list will be fixed by
> node-iconv rebuild.
> 
> 
> Agreed. Node-nodedbi is removed from testing, officially
> now. We can file a (RC) bug against Node-srs for it to _not_
> migrate, same for Node-millstone.
> Nodejs transition is also required for acorn transition,
> from what I read on the mailing list.
> 
> As it's been pending now, for a long time and there's not
> much to be done except fixing these last 2-3 blockers, which
> will be removed (from testing) anyway.
> Would it be a good time to start the transition?
> If yes, It would be great to start in other transitions, :)
> 
> 
> 
> Right now node is waiting upon icu >=  64, which won't be in sid
> before ~may.
> 
> 
> This is probably the time now - may ends with the coming weekend.
> Any updates if this is in sid or when this would get to sid if it
> isn't already?
> 
> 
> It's ready to be built, but not ready to go in testing:
> https://buildd.debian.org/status/package.php?p=nodejs=experimental
> 
> - amd64 some tests won't pass because of network issues
>   I never figured why some build servers fail on this, and some not.
> *  If anyone knows an explanation, that'll help.*
> - armhf, i386: dh_dwz fails because it exhausts memory.
>   Somewhat fixed by ignoring those failures. *Is there a better option ?*
> - mips64el: tools/test.py no longer recognize the arch (it should get it
> from
>   the one mapped in debian/rules). Easy to fix.
> - mipsel: fails to build, OOM as some point.
>   That was on a 8GB memory machine, so i suppose it's bad luck, something
>   else was using memory maybe.
> 
> Jérémy

Hi,

there is a new "needs-internet" restriction in autopkgtest, maybe this
will fix one pb

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] nodejs-12 transition

[Pirate Praveen]

On Mon, May 25, 2020 at 10:51 am, Jérémy Lal  
wrote:

It's ready to be built, but not ready to go in testing:
https://buildd.debian.org/status/package.php?p=nodejs=experimental

- amd64 some tests won't pass because of network issues
  I never figured why some build servers fail on this, and some not.
  If anyone knows an explanation, that'll help.
- armhf, i386: dh_dwz fails because it exhausts memory.
  Somewhat fixed by ignoring those failures. Is there a better option 
?
- mips64el: tools/test.py no longer recognize the arch (it should get 
it from

  the one mapped in debian/rules). Easy to fix.
- mipsel: fails to build, OOM as some point.
  That was on a 8GB memory machine, so i suppose it's bad luck, 
something

  else was using memory maybe.



Can't these be fixed after it hits unstable, given that we really want 
nodejs 12 in bullseye and we can't have nodejs 10 in bullseye?


The earlier it hits unstable, the more testing it can receive.


Jérémy






--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] nodejs-12 transition

[Jérémy Lal]

Le lun. 25 mai 2020 à 09:22, Nilesh Patra  a écrit :

> Hi Jérémy
>
> On Sat, 7 Mar 2020, 14:34 Jérémy Lal,  wrote:
>
>>
>>
>> Le sam. 7 mars 2020 à 06:18, Nilesh Patra  a écrit :
>>
>>>
>>>
>>> I think we should start Node.js 12 migration (with rollup, webpack,
 gulp,...), this will also fix some RC/FTBFS bugs, should we?
 I fixed a lot of failing autopkgtest errors (using [1] list), most of
 the remaining packages in this list will be fixed by node-iconv rebuild.

>>>
>>> Agreed. Node-nodedbi is removed from testing, officially now. We can
>>> file a (RC) bug against Node-srs for it to _not_ migrate, same for
>>> Node-millstone.
>>> Nodejs transition is also required for acorn transition, from what I
>>> read on the mailing list.
>>>
>>> As it's been pending now, for a long time and there's not much to be
>>> done except fixing these last 2-3 blockers, which will be removed (from
>>> testing) anyway.
>>> Would it be a good time to start the transition?
>>> If yes, It would be great to start in other transitions, :)
>>>
>>
>>
>> Right now node is waiting upon icu >=  64, which won't be in sid before
>> ~may.
>>
>
> This is probably the time now - may ends with the coming weekend. Any
> updates if this is in sid or when this would get to sid if it isn't already?
>

It's ready to be built, but not ready to go in testing:
https://buildd.debian.org/status/package.php?p=nodejs=experimental

- amd64 some tests won't pass because of network issues
  I never figured why some build servers fail on this, and some not.
*  If anyone knows an explanation, that'll help.*
- armhf, i386: dh_dwz fails because it exhausts memory.
  Somewhat fixed by ignoring those failures. *Is there a better option ?*
- mips64el: tools/test.py no longer recognize the arch (it should get it
from
  the one mapped in debian/rules). Easy to fix.
- mipsel: fails to build, OOM as some point.
  That was on a 8GB memory machine, so i suppose it's bad luck, something
  else was using memory maybe.

Jérémy

>
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] nodejs-12 transition

[Nilesh Patra]

Hi Jérémy

On Sat, 7 Mar 2020, 14:34 Jérémy Lal,  wrote:

>
>
> Le sam. 7 mars 2020 à 06:18, Nilesh Patra  a écrit :
>
>>
>>
>> I think we should start Node.js 12 migration (with rollup, webpack,
>>> gulp,...), this will also fix some RC/FTBFS bugs, should we?
>>> I fixed a lot of failing autopkgtest errors (using [1] list), most of
>>> the remaining packages in this list will be fixed by node-iconv rebuild.
>>>
>>
>> Agreed. Node-nodedbi is removed from testing, officially now. We can file
>> a (RC) bug against Node-srs for it to _not_ migrate, same for
>> Node-millstone.
>> Nodejs transition is also required for acorn transition, from what I read
>> on the mailing list.
>>
>> As it's been pending now, for a long time and there's not much to be done
>> except fixing these last 2-3 blockers, which will be removed (from testing)
>> anyway.
>> Would it be a good time to start the transition?
>> If yes, It would be great to start in other transitions, :)
>>
>
>
> Right now node is waiting upon icu >=  64, which won't be in sid before
> ~may.
>

This is probably the time now - may ends with the coming weekend. Any
updates if this is in sid or when this would get to sid if it isn't already?

Kind regards
Nilesh

>
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] nodejs-12 transition

[Pirate Praveen]

On Sun, Mar 8, 2020 at 10:50 am, Jérémy Lal  wrote:



Le dim. 8 mars 2020 à 06:04, Pirate Praveen 
 a écrit :



 On 2020, മാർച്ച് 7 2:34:17 PM IST, "Jérémy Lal" 
 wrote:
 >Le sam. 7 mars 2020 à 06:18, Nilesh Patra  a 
écrit

 >:
 >
 >>
 >>
 >> I think we should start Node.js 12 migration (with rollup, 
webpack,

 >>> gulp,...), this will also fix some RC/FTBFS bugs, should we?
 >>> I fixed a lot of failing autopkgtest errors (using [1] list), 
most

 >of
 >>> the remaining packages in this list will be fixed by node-iconv
 >rebuild.
 >>>
 >>
 >> Agreed. Node-nodedbi is removed from testing, officially now. We 
can

 >file
 >> a (RC) bug against Node-srs for it to _not_ migrate, same for
 >> Node-millstone.
 >> Nodejs transition is also required for acorn transition, from 
what I

 >read
 >> on the mailing list.
 >>
 >> As it's been pending now, for a long time and there's not much 
to be

 >done
 >> except fixing these last 2-3 blockers, which will be removed 
(from

 >testing)
 >> anyway.
 >> Would it be a good time to start the transition?
 >> If yes, It would be great to start in other transitions, :)
 >>
 >
 >
 >Right now node is waiting upon icu >=  64, which won't be in sid 
before

 >~may.

 Any blockers for that? Can we try asking release team to fast track 
it?


I don't know. The extra time is to avoid extra work i guess.



I think there is no harm in asking them.

We can just open the transition bug and mention it needs to go with 
icu. They will figure out the best time.




 >There is also a problem with node-acorn (it needs the one in
 >experimental).

 acorn 6 is in unstable.


Oh. Right.




--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] nodejs-12 transition

[Pirate Praveen]

On Sun, Mar 8, 2020 at 10:50 am, Jérémy Lal  wrote:



Le dim. 8 mars 2020 à 06:04, Pirate Praveen 
 a écrit :



 On 2020, മാർച്ച് 7 2:34:17 PM IST, "Jérémy Lal" 
 wrote:
 >Le sam. 7 mars 2020 à 06:18, Nilesh Patra  a 
écrit

 >:
 >
 >>
 >>
 >> I think we should start Node.js 12 migration (with rollup, 
webpack,

 >>> gulp,...), this will also fix some RC/FTBFS bugs, should we?
 >>> I fixed a lot of failing autopkgtest errors (using [1] list), 
most

 >of
 >>> the remaining packages in this list will be fixed by node-iconv
 >rebuild.
 >>>
 >>
 >> Agreed. Node-nodedbi is removed from testing, officially now. We 
can

 >file
 >> a (RC) bug against Node-srs for it to _not_ migrate, same for
 >> Node-millstone.
 >> Nodejs transition is also required for acorn transition, from 
what I

 >read
 >> on the mailing list.
 >>
 >> As it's been pending now, for a long time and there's not much 
to be

 >done
 >> except fixing these last 2-3 blockers, which will be removed 
(from

 >testing)
 >> anyway.
 >> Would it be a good time to start the transition?
 >> If yes, It would be great to start in other transitions, :)
 >>
 >
 >
 >Right now node is waiting upon icu >=  64, which won't be in sid 
before

 >~may.

 Any blockers for that? Can we try asking release team to fast track 
it?


I don't know. The extra time is to avoid extra work i guess.



I think there is no harm in asking them.

We can just open the transition bug and mention it needs to go with 
icu. They will figure out the best time.




 >There is also a problem with node-acorn (it needs the one in
 >experimental).

 acorn 6 is in unstable.


Oh. Right.




--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] nodejs-12 transition

[Pirate Praveen]

On Sun, Mar 8, 2020 at 10:50 am, Jérémy Lal  wrote:



Le dim. 8 mars 2020 à 06:04, Pirate Praveen 
 a écrit :



 On 2020, മാർച്ച് 7 2:34:17 PM IST, "Jérémy Lal" 
 wrote:
 >Le sam. 7 mars 2020 à 06:18, Nilesh Patra  a 
écrit

 >:
 >
 >>
 >>
 >> I think we should start Node.js 12 migration (with rollup, 
webpack,

 >>> gulp,...), this will also fix some RC/FTBFS bugs, should we?
 >>> I fixed a lot of failing autopkgtest errors (using [1] list), 
most

 >of
 >>> the remaining packages in this list will be fixed by node-iconv
 >rebuild.
 >>>
 >>
 >> Agreed. Node-nodedbi is removed from testing, officially now. We 
can

 >file
 >> a (RC) bug against Node-srs for it to _not_ migrate, same for
 >> Node-millstone.
 >> Nodejs transition is also required for acorn transition, from 
what I

 >read
 >> on the mailing list.
 >>
 >> As it's been pending now, for a long time and there's not much 
to be

 >done
 >> except fixing these last 2-3 blockers, which will be removed 
(from

 >testing)
 >> anyway.
 >> Would it be a good time to start the transition?
 >> If yes, It would be great to start in other transitions, :)
 >>
 >
 >
 >Right now node is waiting upon icu >=  64, which won't be in sid 
before

 >~may.

 Any blockers for that? Can we try asking release team to fast track 
it?


I don't know. The extra time is to avoid extra work i guess.



I think there is no harm in asking them.

We can just open the transition bug and mention it needs to go with 
icu. They will figure out the best time.




 >There is also a problem with node-acorn (it needs the one in
 >experimental).

 acorn 6 is in unstable.


Oh. Right.




--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] nodejs-12 transition

[Pirate Praveen]

On Sun, Mar 8, 2020 at 10:50 am, Jérémy Lal  wrote:



Le dim. 8 mars 2020 à 06:04, Pirate Praveen 
 a écrit :



 On 2020, മാർച്ച് 7 2:34:17 PM IST, "Jérémy Lal" 
 wrote:
 >Le sam. 7 mars 2020 à 06:18, Nilesh Patra  a 
écrit

 >:
 >
 >>
 >>
 >> I think we should start Node.js 12 migration (with rollup, 
webpack,

 >>> gulp,...), this will also fix some RC/FTBFS bugs, should we?
 >>> I fixed a lot of failing autopkgtest errors (using [1] list), 
most

 >of
 >>> the remaining packages in this list will be fixed by node-iconv
 >rebuild.
 >>>
 >>
 >> Agreed. Node-nodedbi is removed from testing, officially now. We 
can

 >file
 >> a (RC) bug against Node-srs for it to _not_ migrate, same for
 >> Node-millstone.
 >> Nodejs transition is also required for acorn transition, from 
what I

 >read
 >> on the mailing list.
 >>
 >> As it's been pending now, for a long time and there's not much 
to be

 >done
 >> except fixing these last 2-3 blockers, which will be removed 
(from

 >testing)
 >> anyway.
 >> Would it be a good time to start the transition?
 >> If yes, It would be great to start in other transitions, :)
 >>
 >
 >
 >Right now node is waiting upon icu >=  64, which won't be in sid 
before

 >~may.

 Any blockers for that? Can we try asking release team to fast track 
it?


I don't know. The extra time is to avoid extra work i guess.



I think there is no harm in asking them.

We can just open the transition bug and mention it needs to go with 
icu. They will figure out the best time.




 >There is also a problem with node-acorn (it needs the one in
 >experimental).

 acorn 6 is in unstable.


Oh. Right.




--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] nodejs-12 transition

[Jérémy Lal]

Le dim. 8 mars 2020 à 06:04, Pirate Praveen  a
écrit :

>
>
> On 2020, മാർച്ച് 7 2:34:17 PM IST, "Jérémy Lal"  wrote:
> >Le sam. 7 mars 2020 à 06:18, Nilesh Patra  a écrit
> >:
> >
> >>
> >>
> >> I think we should start Node.js 12 migration (with rollup, webpack,
> >>> gulp,...), this will also fix some RC/FTBFS bugs, should we?
> >>> I fixed a lot of failing autopkgtest errors (using [1] list), most
> >of
> >>> the remaining packages in this list will be fixed by node-iconv
> >rebuild.
> >>>
> >>
> >> Agreed. Node-nodedbi is removed from testing, officially now. We can
> >file
> >> a (RC) bug against Node-srs for it to _not_ migrate, same for
> >> Node-millstone.
> >> Nodejs transition is also required for acorn transition, from what I
> >read
> >> on the mailing list.
> >>
> >> As it's been pending now, for a long time and there's not much to be
> >done
> >> except fixing these last 2-3 blockers, which will be removed (from
> >testing)
> >> anyway.
> >> Would it be a good time to start the transition?
> >> If yes, It would be great to start in other transitions, :)
> >>
> >
> >
> >Right now node is waiting upon icu >=  64, which won't be in sid before
> >~may.
>
> Any blockers for that? Can we try asking release team to fast track it?
>

I don't know. The extra time is to avoid extra work i guess.


>
> >There is also a problem with node-acorn (it needs the one in
> >experimental).
>
> acorn 6 is in unstable.
>

Oh. Right.
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] nodejs-12 transition

[Pirate Praveen]

On 2020, മാർച്ച് 7 2:34:17 PM IST, "Jérémy Lal"  wrote:
>Le sam. 7 mars 2020 à 06:18, Nilesh Patra  a écrit
>:
>
>>
>>
>> I think we should start Node.js 12 migration (with rollup, webpack,
>>> gulp,...), this will also fix some RC/FTBFS bugs, should we?
>>> I fixed a lot of failing autopkgtest errors (using [1] list), most
>of
>>> the remaining packages in this list will be fixed by node-iconv
>rebuild.
>>>
>>
>> Agreed. Node-nodedbi is removed from testing, officially now. We can
>file
>> a (RC) bug against Node-srs for it to _not_ migrate, same for
>> Node-millstone.
>> Nodejs transition is also required for acorn transition, from what I
>read
>> on the mailing list.
>>
>> As it's been pending now, for a long time and there's not much to be
>done
>> except fixing these last 2-3 blockers, which will be removed (from
>testing)
>> anyway.
>> Would it be a good time to start the transition?
>> If yes, It would be great to start in other transitions, :)
>>
>
>
>Right now node is waiting upon icu >=  64, which won't be in sid before
>~may.

Any blockers for that? Can we try asking release team to fast track it?

>There is also a problem with node-acorn (it needs the one in
>experimental).

acorn 6 is in unstable.
>
>Jérémy

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] nodejs-12 transition

[Jérémy Lal]

Le sam. 7 mars 2020 à 06:18, Nilesh Patra  a écrit :

>
>
> I think we should start Node.js 12 migration (with rollup, webpack,
>> gulp,...), this will also fix some RC/FTBFS bugs, should we?
>> I fixed a lot of failing autopkgtest errors (using [1] list), most of
>> the remaining packages in this list will be fixed by node-iconv rebuild.
>>
>
> Agreed. Node-nodedbi is removed from testing, officially now. We can file
> a (RC) bug against Node-srs for it to _not_ migrate, same for
> Node-millstone.
> Nodejs transition is also required for acorn transition, from what I read
> on the mailing list.
>
> As it's been pending now, for a long time and there's not much to be done
> except fixing these last 2-3 blockers, which will be removed (from testing)
> anyway.
> Would it be a good time to start the transition?
> If yes, It would be great to start in other transitions, :)
>


Right now node is waiting upon icu >=  64, which won't be in sid before
~may.
There is also a problem with node-acorn (it needs the one in experimental).

Jérémy
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] nodejs-12 transition

[Nilesh Patra]

I think we should start Node.js 12 migration (with rollup, webpack,
> gulp,...), this will also fix some RC/FTBFS bugs, should we?
> I fixed a lot of failing autopkgtest errors (using [1] list), most of
> the remaining packages in this list will be fixed by node-iconv rebuild.
>

Agreed. Node-nodedbi is removed from testing, officially now. We can file a
(RC) bug against Node-srs for it to _not_ migrate, same for Node-millstone.
Nodejs transition is also required for acorn transition, from what I read
on the mailing list.

As it's been pending now, for a long time and there's not much to be done
except fixing these last 2-3 blockers, which will be removed (from testing)
anyway.
Would it be a good time to start the transition?
If yes, It would be great to start in other transitions, :)

Thanks and regards
Nilesh
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] nodejs-12 transition

[Xavier]

Le 03/03/2020 à 16:01, Xavier a écrit :
> Le 03/03/2020 à 11:01, Bas Couwenberg a écrit :
>> On 2020-03-03 10:39, Jérémy Lal wrote:
  * node-srs (no more in testing)
>>>
>>> It needs much more work, as the latest version depends on node-gdal
>>> bindings.
>>
>> node-srs is required for node-millstone, which in turn is required for
>> node-carto.
>>
>> None of these packages are in testing, perhaps they should be removed
>> from unstable as well.
>>
>> It doesn't seem like any one will be willing and able to update
>> node-carto in the foreseeable future, which makes me think we should cut
>> our losses.
>>
>> Kind Regards,
>>
>> Bas
> 
> Hi,
> 
> node-carto has already been removed from archive. Here is the `dak`
> result. OK to remove it from archive or just fill a RC bug to remove it
> only from testing?

I think we should start Node.js 12 migration (with rollup, webpack,
gulp,...), this will also fix some RC/FTBFS bugs, should we?
I fixed a lot of failing autopkgtest errors (using [1] list), most of
the remaining packages in this list will be fixed by node-iconv rebuild.

Cheers,
Xavier

[1]:
https://release.debian.org/britney/pseudo-excuses-experimental.html#nodejs

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] nodejs-12 transition

[Sebastiaan Couwenberg]

On 3/3/20 4:01 PM, Xavier wrote:
> Le 03/03/2020 à 11:01, Bas Couwenberg a écrit :
>> On 2020-03-03 10:39, Jérémy Lal wrote:
  * node-srs (no more in testing)
>>>
>>> It needs much more work, as the latest version depends on node-gdal
>>> bindings.
>>
>> node-srs is required for node-millstone, which in turn is required for
>> node-carto.
>>
>> None of these packages are in testing, perhaps they should be removed
>> from unstable as well.
>>
>> It doesn't seem like any one will be willing and able to update
>> node-carto in the foreseeable future, which makes me think we should cut
>> our losses.
> 
> node-carto has already been removed from archive.

Only from testing according to:

 https://tracker.debian.org/pkg/node-carto

> Here is the `dak`
> result. OK to remove it from archive or just fill a RC bug to remove it
> only from testing?

It's already removed from testing, it and its rdeps should be removed
from unstable as well.

I'll filed #953031 to remove openstreetmap-carto which build depends on
node-carto.

> $ dak -rn node-srs

You need to use -Rn:

$ dak rm -Rn node-carto
Will remove the following packages from unstable:

node-carto |0.9.5-2 | source, all

Maintainer: Debian Javascript Maintainers


--- Reason ---

--

Checking reverse dependencies...
# Broken Build-Depends:
openstreetmap-carto: node-carto

Dependency problem found.


Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] nodejs-12 transition

[Xavier]

Le 03/03/2020 à 11:01, Bas Couwenberg a écrit :
> On 2020-03-03 10:39, Jérémy Lal wrote:
>>>  * node-srs (no more in testing)
>>
>> It needs much more work, as the latest version depends on node-gdal
>> bindings.
> 
> node-srs is required for node-millstone, which in turn is required for
> node-carto.
> 
> None of these packages are in testing, perhaps they should be removed
> from unstable as well.
> 
> It doesn't seem like any one will be willing and able to update
> node-carto in the foreseeable future, which makes me think we should cut
> our losses.
> 
> Kind Regards,
> 
> Bas

Hi,

node-carto has already been removed from archive. Here is the `dak`
result. OK to remove it from archive or just fill a RC bug to remove it
only from testing?

$ dak -rn node-srs
Will remove the following packages from unstable:

  node-srs | 0.4.8+dfsg-4 | source
  node-srs | 0.4.8+dfsg-4+b1 | amd64, arm64, armhf, i386, mips64el,
mipsel, ppc64el, s390x

Maintainer: Debian Javascript Maintainers


--- Reason ---

--

Checking reverse dependencies...
# Broken Depends:
node-millstone: node-millstone

# Broken Build-Depends:
node-millstone: node-srs

Dependency problem found.

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] nodejs-12 transition

[Xavier]

Hi,

This package is not required by any other package (I introduced it for a 
package that will not be integrated in Bullseye).
Proposition : fill a RC bug "not compatible with Node.JS 12" and ask d'or 
testing-only-removal

Then we will wait for upstream update (bug already opened)

Regards,
Xavier

Le 3 mars 2020 11:29:15 GMT+01:00, "Jérémy Lal"  a écrit :
>Le mar. 3 mars 2020 à 10:41, Jérémy Lal  a écrit :
>
>>
>>
>> Le mar. 3 mars 2020 à 10:39, Jérémy Lal  a écrit :
>>
>>>
>>>
>>> Le mar. 3 mars 2020 à 06:47, Xavier  a écrit :
>>>
 Le 03/02/2020 à 20:16, Xavier a écrit :
 > Le 02/02/2020 à 11:01, Xavier a écrit :
 >> There are no 2 packages to fix at least. I did my best with partial
 >> patches but I need help to fix them:
 >>  * node-srs: new upstream version not compatible with current libgdal,
 >>  need help to fix current version
 >>  * node-nodedbi: I'm unable to fix one issue (Nan::Value to
 std::string)
 >>
 >> Other packages looks good or were previously broken (some of them in
 >> experimental)
 >
 > Is there a C++/Node/Nan expert that can take a look at these 2
 packages?

 Hi,

 I fixed a lot of packages that (autopkgtest) fail with Node.js ≥ 12.
 Please help to fix last packages:
  * node-nodedbi

>>>
>>> That one builds but i have troubles running tests in experimental in my
>>> setup.
>>>
>>> https://salsa.debian.org/js-team/node-nodedbi/-/merge_requests/new?merge_request%5Bsource_branch%5D=compat-with-nodejs12
>>>
>>
>> also i forgot to add that it doesn't need to force nodejs >= 12
>> since it builds fine with nodejs 10 with the patch.
>>
>
>I'm testing manually node-nodedbi and it doesn't connect to a DB
>successfully.
>It's difficult to debug: i can't find any libdbi client.

-- 
Envoyé de mon appareil Android avec Courriel K-9 Mail. Veuillez excuser ma 
brièveté.-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] nodejs-12 transition

[Jérémy Lal]

Le mar. 3 mars 2020 à 10:41, Jérémy Lal  a écrit :

>
>
> Le mar. 3 mars 2020 à 10:39, Jérémy Lal  a écrit :
>
>>
>>
>> Le mar. 3 mars 2020 à 06:47, Xavier  a écrit :
>>
>>> Le 03/02/2020 à 20:16, Xavier a écrit :
>>> > Le 02/02/2020 à 11:01, Xavier a écrit :
>>> >> There are no 2 packages to fix at least. I did my best with partial
>>> >> patches but I need help to fix them:
>>> >>  * node-srs: new upstream version not compatible with current libgdal,
>>> >>  need help to fix current version
>>> >>  * node-nodedbi: I'm unable to fix one issue (Nan::Value to
>>> std::string)
>>> >>
>>> >> Other packages looks good or were previously broken (some of them in
>>> >> experimental)
>>> >
>>> > Is there a C++/Node/Nan expert that can take a look at these 2
>>> packages?
>>>
>>> Hi,
>>>
>>> I fixed a lot of packages that (autopkgtest) fail with Node.js ≥ 12.
>>> Please help to fix last packages:
>>>  * node-nodedbi
>>>
>>
>> That one builds but i have troubles running tests in experimental in my
>> setup.
>>
>> https://salsa.debian.org/js-team/node-nodedbi/-/merge_requests/new?merge_request%5Bsource_branch%5D=compat-with-nodejs12
>>
>
> also i forgot to add that it doesn't need to force nodejs >= 12
> since it builds fine with nodejs 10 with the patch.
>

I'm testing manually node-nodedbi and it doesn't connect to a DB
successfully.
It's difficult to debug: i can't find any libdbi client.
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] nodejs-12 transition

[Bas Couwenberg]

On 2020-03-03 10:39, Jérémy Lal wrote:

 * node-srs (no more in testing)


It needs much more work, as the latest version depends on node-gdal
bindings.


node-srs is required for node-millstone, which in turn is required for 
node-carto.


None of these packages are in testing, perhaps they should be removed 
from unstable as well.


It doesn't seem like any one will be willing and able to update 
node-carto in the foreseeable future, which makes me think we should cut 
our losses.


Kind Regards,

Bas

--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] nodejs-12 transition

[Jérémy Lal]

Le mar. 3 mars 2020 à 06:47, Xavier  a écrit :

> Le 03/02/2020 à 20:16, Xavier a écrit :
> > Le 02/02/2020 à 11:01, Xavier a écrit :
> >> There are no 2 packages to fix at least. I did my best with partial
> >> patches but I need help to fix them:
> >>  * node-srs: new upstream version not compatible with current libgdal,
> >>  need help to fix current version
> >>  * node-nodedbi: I'm unable to fix one issue (Nan::Value to std::string)
> >>
> >> Other packages looks good or were previously broken (some of them in
> >> experimental)
> >
> > Is there a C++/Node/Nan expert that can take a look at these 2 packages?
>
> Hi,
>
> I fixed a lot of packages that (autopkgtest) fail with Node.js ≥ 12.
> Please help to fix last packages:
>  * node-nodedbi
>

That one builds but i have troubles running tests in experimental in my
setup.
https://salsa.debian.org/js-team/node-nodedbi/-/merge_requests/new?merge_request%5Bsource_branch%5D=compat-with-nodejs12


>  * node-srs (no more in testing)
>

It needs much more work, as the latest version depends on node-gdal
bindings.

Jérémy
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] nodejs-12 transition

[Jérémy Lal]

Le mar. 3 mars 2020 à 10:39, Jérémy Lal  a écrit :

>
>
> Le mar. 3 mars 2020 à 06:47, Xavier  a écrit :
>
>> Le 03/02/2020 à 20:16, Xavier a écrit :
>> > Le 02/02/2020 à 11:01, Xavier a écrit :
>> >> There are no 2 packages to fix at least. I did my best with partial
>> >> patches but I need help to fix them:
>> >>  * node-srs: new upstream version not compatible with current libgdal,
>> >>  need help to fix current version
>> >>  * node-nodedbi: I'm unable to fix one issue (Nan::Value to
>> std::string)
>> >>
>> >> Other packages looks good or were previously broken (some of them in
>> >> experimental)
>> >
>> > Is there a C++/Node/Nan expert that can take a look at these 2 packages?
>>
>> Hi,
>>
>> I fixed a lot of packages that (autopkgtest) fail with Node.js ≥ 12.
>> Please help to fix last packages:
>>  * node-nodedbi
>>
>
> That one builds but i have troubles running tests in experimental in my
> setup.
>
> https://salsa.debian.org/js-team/node-nodedbi/-/merge_requests/new?merge_request%5Bsource_branch%5D=compat-with-nodejs12
>

also i forgot to add that it doesn't need to force nodejs >= 12
since it builds fine with nodejs 10 with the patch.
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] nodejs-12 transition

[Xavier]

Le 03/02/2020 à 20:16, Xavier a écrit :
> Le 02/02/2020 à 11:01, Xavier a écrit :
>> There are no 2 packages to fix at least. I did my best with partial
>> patches but I need help to fix them:
>>  * node-srs: new upstream version not compatible with current libgdal,
>>  need help to fix current version
>>  * node-nodedbi: I'm unable to fix one issue (Nan::Value to std::string)
>>
>> Other packages looks good or were previously broken (some of them in
>> experimental)
> 
> Is there a C++/Node/Nan expert that can take a look at these 2 packages?

Hi,

I fixed a lot of packages that (autopkgtest) fail with Node.js ≥ 12.
Please help to fix last packages:
 * node-nodedbi
 * node-srs (no more in testing)

https://salsa.debian.org/js-team/nodejs/-/wikis/Transition-to-Nodejs-12-for-Debian-Unstable

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] nodejs-12 transition

[Nilesh Patra]

On Fri, 7 Feb 2020, 11:44 Xavier,  wrote:

> Le 07/02/2020 à 06:34, Nilesh Patra a écrit :
> >
> >
> > On Fri, 7 Feb 2020, 10:57 Xavier,  > > wrote:
> >
> > Le 07/02/2020 à 06:24, Nilesh Patra a écrit :
> > >
> > >
> > > On Fri, 7 Feb 2020, 03:58 Xavier,  > 
> > > >> wrote:
> > >
> > > Did you update your apt-cacher files ?
> > >
> > >
> > > Yes, I did. I seem to get the same error.
> >
> > Could you give me a way to reproduce?
> >
> >
> > Ofcourse!
> > sbuild on the package rainloop, in the team repo[1] gives me that error.
> >
> > [1]: https://salsa.debian.org/js-team/rainloop
>
> First, replace node-uglify by uglifyjs (or terser): this package
> generates conflicts
>

Thanks!
However, the error still doesn't go away.(on replacing with terser).
I think that there is a problem with the dependencies being installed.
Is only node-babel-cli not the correct way to get node-babel-runtime, or am
I missing another dependency?
I am not sure about it, and need your help here.
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] nodejs-12 transition

[Xavier]

Le 07/02/2020 à 06:34, Nilesh Patra a écrit :
> 
> 
> On Fri, 7 Feb 2020, 10:57 Xavier,  > wrote:
> 
> Le 07/02/2020 à 06:24, Nilesh Patra a écrit :
> >
> >
> > On Fri, 7 Feb 2020, 03:58 Xavier,  
> > >> wrote:
> >
> >     Did you update your apt-cacher files ?
> >
> >
> > Yes, I did. I seem to get the same error.
> 
> Could you give me a way to reproduce?
> 
> 
> Ofcourse!
> sbuild on the package rainloop, in the team repo[1] gives me that error.
> 
> [1]: https://salsa.debian.org/js-team/rainloop

First, replace node-uglify by uglifyjs (or terser): this package
generates conflicts

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] nodejs-12 transition

[Nilesh Patra]

On Fri, 7 Feb 2020, 10:57 Xavier,  wrote:

> Le 07/02/2020 à 06:24, Nilesh Patra a écrit :
> >
> >
> > On Fri, 7 Feb 2020, 03:58 Xavier,  > > wrote:
> >
> > Did you update your apt-cacher files ?
> >
> >
> > Yes, I did. I seem to get the same error.
>
> Could you give me a way to reproduce?
>

Ofcourse!
sbuild on the package rainloop, in the team repo[1] gives me that error.

[1]: https://salsa.debian.org/js-team/rainloop

>
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] nodejs-12 transition

[Xavier]

Le 07/02/2020 à 06:24, Nilesh Patra a écrit :
> 
> 
> On Fri, 7 Feb 2020, 03:58 Xavier,  > wrote:
> 
> Did you update your apt-cacher files ?
> 
> 
> Yes, I did. I seem to get the same error.

Could you give me a way to reproduce?

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] nodejs-12 transition

[Nilesh Patra]

On Fri, 7 Feb 2020, 03:58 Xavier,  wrote:

> Did you update your apt-cacher files ?
>

Yes, I did. I seem to get the same error.
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] nodejs-12 transition

[Xavier]

Did you update your apt-cacher files ?

Le 6 février 2020 22:20:38 GMT+01:00, Nilesh Patra  a 
écrit :
>On Fri, 7 Feb 2020 at 01:23, Xavier  wrote:
>
>> Le 06/02/2020 à 19:19, Nilesh Patra a écrit :
>> > Hi,
>> > I am finding these errors in a few packages:
>> >
>> > ERROR in
>> >
>>
>/usr/share/nodejs/babel-runtime/core-js/object/get-own-property-descriptor.js
>> > Module not found: Error: Can't resolve
>> > 'core-js/library/fn/object/get-own-property-descriptor' in
>> > '/usr/share/nodejs/babel-runtime/core-js/object'
>> >  @
>> >
>>
>/usr/share/nodejs/babel-runtime/core-js/object/get-own-property-descriptor.js
>> > 1:30-94
>> >  @ ./dev/View/Popup/Compose.js
>> >  @ ./dev/App/User.js
>> >  @ ./dev/app.js
>> >
>> > When I looked at the file, it looks like:
>> >
>> > [~]$ cat
>> >
>>
>/usr/share/nodejs/babel-runtime/core-js/object/get-own-property-descriptor.js
>> > module.exports = { "default":
>> > require("core-js/library/fn/object/get-own-property-descriptor"),
>> > __esModule: true };
>> >
>> > To me, it looks like using core-js@2, instead of 3(latest in
>debian). It
>> > looks like an issue with babel-runtime (one of the provides of
>> > node-babel). Should node-babel be fixed accordingly,
>> > or is there a workaround here, instead?
>> > I am not very sure of that, and need help to fix this issue.
>> > Could anyone please help me out?
>> > That would be great.
>> >
>> > Thanks and regards
>> > Nilesh
>>
>> Hi,
>>
>> The file is here (core-js 2 is embedded):
>>
>>
>/usr/share/nodejs/babel-runtime/node_modules/core-js/library/fn/object/get-own-property-descriptor.js
>>
>> Which version of node-babel do you use ?
>>
>
>I was using sbuild, so it should pick-up the latest one in unstable.
>The version installed on my system in 6.26.0.
>
>Current testing version:
>> $ cat
>>
>> 
>/usr/share/nodejs/babel-runtime/core-js/object/get-own-property-descriptor.js
>> require('../../modules/es6.object.get-own-property-descriptor');
>> var $Object = require('../../modules/_core').Object;
>> module.exports = function getOwnPropertyDescriptor(it, key) {
>>   return $Object.getOwnPropertyDescriptor(it, key);
>> };
>>
>
>Strange, :/ I even installed it in a clean chroot, and seem to get the
>same
>log which I sent earlier.
>To ensure: apt install node-babel-cli is what you used to get
>node-babel-runtime, right?
>
>
>> Which seems to work fine
>>
>> --
>> Pkg-javascript-devel mailing list
>> Pkg-javascript-devel@alioth-lists.debian.net
>>
>>
>https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

-- 
Envoyé de mon appareil Android avec Courriel K-9 Mail. Veuillez excuser ma 
brièveté.-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] nodejs-12 transition

[Nilesh Patra]

On Fri, 7 Feb 2020 at 01:23, Xavier  wrote:

> Le 06/02/2020 à 19:19, Nilesh Patra a écrit :
> > Hi,
> > I am finding these errors in a few packages:
> >
> > ERROR in
> >
> /usr/share/nodejs/babel-runtime/core-js/object/get-own-property-descriptor.js
> > Module not found: Error: Can't resolve
> > 'core-js/library/fn/object/get-own-property-descriptor' in
> > '/usr/share/nodejs/babel-runtime/core-js/object'
> >  @
> >
> /usr/share/nodejs/babel-runtime/core-js/object/get-own-property-descriptor.js
> > 1:30-94
> >  @ ./dev/View/Popup/Compose.js
> >  @ ./dev/App/User.js
> >  @ ./dev/app.js
> >
> > When I looked at the file, it looks like:
> >
> > [~]$ cat
> >
> /usr/share/nodejs/babel-runtime/core-js/object/get-own-property-descriptor.js
> > module.exports = { "default":
> > require("core-js/library/fn/object/get-own-property-descriptor"),
> > __esModule: true };
> >
> > To me, it looks like using core-js@2, instead of 3(latest in debian). It
> > looks like an issue with babel-runtime (one of the provides of
> > node-babel). Should node-babel be fixed accordingly,
> > or is there a workaround here, instead?
> > I am not very sure of that, and need help to fix this issue.
> > Could anyone please help me out?
> > That would be great.
> >
> > Thanks and regards
> > Nilesh
>
> Hi,
>
> The file is here (core-js 2 is embedded):
>
> /usr/share/nodejs/babel-runtime/node_modules/core-js/library/fn/object/get-own-property-descriptor.js
>
> Which version of node-babel do you use ?
>

I was using sbuild, so it should pick-up the latest one in unstable.
The version installed on my system in 6.26.0.

Current testing version:
> $ cat
>
>  /usr/share/nodejs/babel-runtime/core-js/object/get-own-property-descriptor.js
> require('../../modules/es6.object.get-own-property-descriptor');
> var $Object = require('../../modules/_core').Object;
> module.exports = function getOwnPropertyDescriptor(it, key) {
>   return $Object.getOwnPropertyDescriptor(it, key);
> };
>

Strange, :/ I even installed it in a clean chroot, and seem to get the same
log which I sent earlier.
To ensure: apt install node-babel-cli is what you used to get
node-babel-runtime, right?


> Which seems to work fine
>
> --
> Pkg-javascript-devel mailing list
> Pkg-javascript-devel@alioth-lists.debian.net
>
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] nodejs-12 transition

[Xavier]

Le 06/02/2020 à 19:19, Nilesh Patra a écrit :
> Hi,
> I am finding these errors in a few packages:
> 
> ERROR in
> /usr/share/nodejs/babel-runtime/core-js/object/get-own-property-descriptor.js
> Module not found: Error: Can't resolve
> 'core-js/library/fn/object/get-own-property-descriptor' in
> '/usr/share/nodejs/babel-runtime/core-js/object'
>  @
> /usr/share/nodejs/babel-runtime/core-js/object/get-own-property-descriptor.js
> 1:30-94
>  @ ./dev/View/Popup/Compose.js
>  @ ./dev/App/User.js
>  @ ./dev/app.js
> 
> When I looked at the file, it looks like:
> 
> [~]$ cat
> /usr/share/nodejs/babel-runtime/core-js/object/get-own-property-descriptor.js
> module.exports = { "default":
> require("core-js/library/fn/object/get-own-property-descriptor"),
> __esModule: true };
> 
> To me, it looks like using core-js@2, instead of 3(latest in debian). It
> looks like an issue with babel-runtime (one of the provides of
> node-babel). Should node-babel be fixed accordingly,
> or is there a workaround here, instead?
> I am not very sure of that, and need help to fix this issue.
> Could anyone please help me out?
> That would be great.
> 
> Thanks and regards
> Nilesh

Hi,

The file is here (core-js 2 is embedded):
/usr/share/nodejs/babel-runtime/node_modules/core-js/library/fn/object/get-own-property-descriptor.js

Which version of node-babel do you use ?

Current testing version:
$ cat
 /usr/share/nodejs/babel-runtime/core-js/object/get-own-property-descriptor.js
require('../../modules/es6.object.get-own-property-descriptor');
var $Object = require('../../modules/_core').Object;
module.exports = function getOwnPropertyDescriptor(it, key) {
  return $Object.getOwnPropertyDescriptor(it, key);
};

Which seems to work fine

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] nodejs-12 transition

[Nilesh Patra]

Hi,
I am finding these errors in a few packages:

ERROR in
/usr/share/nodejs/babel-runtime/core-js/object/get-own-property-descriptor.js
Module not found: Error: Can't resolve
'core-js/library/fn/object/get-own-property-descriptor' in
'/usr/share/nodejs/babel-runtime/core-js/object'
 @
/usr/share/nodejs/babel-runtime/core-js/object/get-own-property-descriptor.js
1:30-94
 @ ./dev/View/Popup/Compose.js
 @ ./dev/App/User.js
 @ ./dev/app.js

When I looked at the file, it looks like:

[~]$ cat
/usr/share/nodejs/babel-runtime/core-js/object/get-own-property-descriptor.js
module.exports = { "default":
require("core-js/library/fn/object/get-own-property-descriptor"),
__esModule: true };

To me, it looks like using core-js@2, instead of 3(latest in debian). It
looks like an issue with babel-runtime (one of the provides of node-babel).
Should node-babel be fixed accordingly,
or is there a workaround here, instead?
I am not very sure of that, and need help to fix this issue.
Could anyone please help me out?
That would be great.

Thanks and regards
Nilesh
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] nodejs-12 transition

[Xavier]

Le 03/02/2020 à 20:16, Xavier a écrit :
> Le 02/02/2020 à 11:01, Xavier a écrit :
>> There are no 2 packages to fix at least. I did my best with partial
>> patches but I need help to fix them:
>>  * node-srs: new upstream version not compatible with current libgdal,
>>  need help to fix current version
>>  * node-nodedbi: I'm unable to fix one issue (Nan::Value to std::string)
>>
>> Other packages looks good or were previously broken (some of them in
>> experimental)
> 
> Is there a C++/Node/Nan expert that can take a look at these 2 packages?

For later: it seems that there will be perhaps a problem between acorn-6
package and mocha build (around node-acorn-dynamic-import). To be tested.

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] nodejs-12 transition

[Jérémy Lal]

Le lun. 3 févr. 2020 à 20:39, Nilesh Patra  a écrit :

>
>
> On Tue, 4 Feb 2020, 00:46 Xavier,  wrote:
>
>> Le 02/02/2020 à 11:01, Xavier a écrit :
>> > There are no 2 packages to fix at least. I did my best with partial
>> > patches but I need help to fix them:
>> >  * node-srs: new upstream version not compatible with current libgdal,
>> >  need help to fix current version
>> >  * node-nodedbi: I'm unable to fix one issue (Nan::Value to std::string)
>> >
>> > Other packages looks good or were previously broken (some of them in
>> > experimental)
>>
>> Is there a C++/Node/Nan expert that can take a look at these 2 packages?
>>
>
> I think Jeremy can help here. He had mentioned to help with C++ add-ons in
> the list earlier, and he also maintains node-nan.
> Jeremy, could you please help us with fixing these two packages?
> That would be indeed, great, as they are the last blockers in the
> transition.
>

Yes, i'll have a look.
Jérémy

>
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] nodejs-12 transition

[Nilesh Patra]

On Tue, 4 Feb 2020, 00:46 Xavier,  wrote:

> Le 02/02/2020 à 11:01, Xavier a écrit :
> > There are no 2 packages to fix at least. I did my best with partial
> > patches but I need help to fix them:
> >  * node-srs: new upstream version not compatible with current libgdal,
> >  need help to fix current version
> >  * node-nodedbi: I'm unable to fix one issue (Nan::Value to std::string)
> >
> > Other packages looks good or were previously broken (some of them in
> > experimental)
>
> Is there a C++/Node/Nan expert that can take a look at these 2 packages?
>

I think Jeremy can help here. He had mentioned to help with C++ add-ons in
the list earlier, and he also maintains node-nan.
Jeremy, could you please help us with fixing these two packages?
That would be indeed, great, as they are the last blockers in the
transition.

Thanks and regards
Nilesh

>

> --
> Pkg-javascript-devel mailing list
> Pkg-javascript-devel@alioth-lists.debian.net
>
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] nodejs-12 transition

[Xavier]

Le 02/02/2020 à 11:01, Xavier a écrit :
> There are no 2 packages to fix at least. I did my best with partial
> patches but I need help to fix them:
>  * node-srs: new upstream version not compatible with current libgdal,
>  need help to fix current version
>  * node-nodedbi: I'm unable to fix one issue (Nan::Value to std::string)
> 
> Other packages looks good or were previously broken (some of them in
> experimental)

Is there a C++/Node/Nan expert that can take a look at these 2 packages?

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] nodejs-12 transition

[Nilesh Patra]

On Sun, 2 Feb 2020 at 20:23, Xavier  wrote:

> Le 02/02/2020 à 14:45, Nilesh Patra a écrit :
> > Hi,
> > I was trying to fix node-jsonld. There were a lot of 'Module not found'
> > errors, and resolving paths in webpack.config.js helped.
> > However, there are a few core-js related errors which are still there. I
> > am not sure why that is the case. I suspect that this is likely due to
> > incompatible version of core-js.
> > Could someone help me here, to understand the issue, and a probable fix?
> > That would be great!
> > Pasting the logs:
> >
> > ERROR in multi core-js/fn/array/from core-js/fn/array/includes
> > core-js/fn/map core-js/fn/object/assign core-js/fn/promise
> > core-js/fn/set core-js/fn/string/starts-with core-js/fn/symbol
> > ./lib/index.js
> > Module not found: Error: Can't resolve 'core-js/fn/array/from' in
> > '/<>'
> >  @ multi core-js/fn/array/from core-js/fn/array/includes
> > core-js/fn/map core-js/fn/object/assign core-js/fn/promise
> > core-js/fn/set core-js/fn/string/starts-with core-js/fn/symbol
> > ./lib/index.js
>
> Hi,
>
> try to replace code-js/fn by core-js/features
>

Yea, I had realised that.
Thank you, :)


>
> > [There are a few more of similar kind, related to core-js ^]
> >
> > Thanks & Regards
> > Nilesh
>
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] nodejs-12 transition

[Xavier]

Le 02/02/2020 à 14:45, Nilesh Patra a écrit :
> Hi,
> I was trying to fix node-jsonld. There were a lot of 'Module not found'
> errors, and resolving paths in webpack.config.js helped.
> However, there are a few core-js related errors which are still there. I
> am not sure why that is the case. I suspect that this is likely due to
> incompatible version of core-js.
> Could someone help me here, to understand the issue, and a probable fix?
> That would be great!
> Pasting the logs:
> 
>     ERROR in multi core-js/fn/array/from core-js/fn/array/includes
> core-js/fn/map core-js/fn/object/assign core-js/fn/promise
> core-js/fn/set core-js/fn/string/starts-with core-js/fn/symbol
> ./lib/index.js
>     Module not found: Error: Can't resolve 'core-js/fn/array/from' in
> '/<>'
>      @ multi core-js/fn/array/from core-js/fn/array/includes
> core-js/fn/map core-js/fn/object/assign core-js/fn/promise
> core-js/fn/set core-js/fn/string/starts-with core-js/fn/symbol
> ./lib/index.js

Hi,

try to replace code-js/fn by core-js/features

> [There are a few more of similar kind, related to core-js ^]
> 
> Thanks & Regards
> Nilesh

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] nodejs-12 transition

[Nilesh Patra]

On Sun, 2 Feb 2020 at 19:15, Nilesh Patra  wrote:

> Hi,
> I was trying to fix node-jsonld. There were a lot of 'Module not found'
> errors, and resolving paths in webpack.config.js helped.
> However, there are a few core-js related errors which are still there. I
> am not sure why that is the case. I suspect that this is likely due to
> incompatible version of core-js.
> Could someone help me here, to understand the issue, and a probable fix?
> That would be great!
> Pasting the logs:
>
> ERROR in multi core-js/fn/array/from core-js/fn/array/includes
> core-js/fn/map core-js/fn/object/assign core-js/fn/promise core-js/fn/set
> core-js/fn/string/starts-with core-js/fn/symbol ./lib/index.js
> Module not found: Error: Can't resolve 'core-js/fn/array/from' in
> '/<>'
>  @ multi core-js/fn/array/from core-js/fn/array/includes
> core-js/fn/map core-js/fn/object/assign core-js/fn/promise core-js/fn/set
> core-js/fn/string/starts-with core-js/fn/symbol ./lib/index.js
>
> [There are a few more of similar kind, related to core-js ^]
>
> Thanks & Regards
> Nilesh
>

I observed that I needed to change core-js paths individually as well in
webpack.config.js. That worked.
Thanks
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] nodejs-12 transition

[Xavier]

There are no 2 packages to fix at least. I did my best with partial
patches but I need help to fix them:
 * node-srs: new upstream version not compatible with current libgdal,
 need help to fix current version
 * node-nodedbi: I'm unable to fix one issue (Nan::Value to std::string)

Other packages looks good or were previously broken (some of them in
experimental)

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] nodejs-12 transition

[Xavier]

I just sorted packages in wiki [1] to separate packages that need to be
fixed for Node.js 12 migration (OK before) and already-buggy packages.
Then first TODO list length is 17 ;-)

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] nodejs-12 transition

[Jérémy Lal]

Le dim. 19 janv. 2020 à 16:38, Pirate Praveen  a
écrit :

>
>
> On ഞാ, Jan 19, 2020 at 11:33, Jérémy Lal 
> wrote:
> >
> >
> > Le dim. 19 janv. 2020 à 07:54, Pirate Praveen
> >  a écrit :
> >>
> >>
> >>  On 2020, ജനുവരി 19 2:32:01 AM IST, "Jérémy Lal"
> >>  wrote:
> >>
> >>  >The problem is the "build-dep-resolver" here.
> >>
> >>  Did you reproduce the error with aptitude and not with aspcud?
> >> aptitude was working even in cases where aspcud failed so most of us
> >> switched to aptitude.
> >
> > Yes, exactly. You need the resolver to pull build-deps from
> > expertimental, not from sid.
> >
>
> May be I'm missing something here (did you really get two different
> results when changing aptitude with aspcud?).
>

YES

aptitude does pull package from experimental if build dependency cannot
> be satisfied from unstable, and that is how we are expected to build in
> experimental. I use aptitude build-resolver always for building
> packages in experimental that needs build dependencies from
> experimental and never faced an issue till now.
>

Well, I don't know about that. I just used another resolver and it didn't
fail.
Maybe it builds using node 12 and test using node 10 ?

Jérémy
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] nodejs-12 transition

[Pirate Praveen]

On ഞാ, Jan 19, 2020 at 11:33, Jérémy Lal  
wrote:



Le dim. 19 janv. 2020 à 07:54, Pirate Praveen 
 a écrit :



 On 2020, ജനുവരി 19 2:32:01 AM IST, "Jérémy Lal" 
 wrote:


 >The problem is the "build-dep-resolver" here.

 Did you reproduce the error with aptitude and not with aspcud? 
aptitude was working even in cases where aspcud failed so most of us 
switched to aptitude.


Yes, exactly. You need the resolver to pull build-deps from 
expertimental, not from sid.




May be I'm missing something here (did you really get two different 
results when changing aptitude with aspcud?).


aptitude does pull package from experimental if build dependency cannot 
be satisfied from unstable, and that is how we are expected to build in 
experimental. I use aptitude build-resolver always for building 
packages in experimental that needs build dependencies from 
experimental and never faced an issue till now.



Jérémy




--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] nodejs-12 transition

[Jérémy Lal]

Le dim. 19 janv. 2020 à 07:54, Pirate Praveen  a
écrit :

>
>
> On 2020, ജനുവരി 19 2:32:01 AM IST, "Jérémy Lal"  wrote:
>
> >The problem is the "build-dep-resolver" here.
>
> Did you reproduce the error with aptitude and not with aspcud? aptitude
> was working even in cases where aspcud failed so most of us switched to
> aptitude.
>

Yes, exactly. You need the resolver to pull build-deps from expertimental,
not from sid.

Jérémy
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] nodejs-12 transition

[Pirate Praveen]

On 2020, ജനുവരി 19 2:32:01 AM IST, "Jérémy Lal"  wrote:

>The problem is the "build-dep-resolver" here.

Did you reproduce the error with aptitude and not with aspcud? aptitude was 
working even in cases where aspcud failed so most of us switched to aptitude.
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] nodejs-12 transition

[Jérémy Lal]

Le sam. 18 janv. 2020 à 21:51, Nilesh Patra  a écrit :

>
>
> On Sun, 19 Jan 2020, 01:31 Nilesh Patra,  wrote:
>
>>
>>
>> On Sat, 18 Jan 2020 at 13:33, Jérémy Lal  wrote:
>>
>>> Nilesh: how to you build node-nan ?
>>> Using
>>> gbp buildpackage -d experimental --extra-repository='deb
>>> http://httpredir.debian.org/debian experimental main'
>>> --build-dep-resolver=aspcud
>>> tests + autopkgtests are all right doing that.
>>>
>>
>> Hi,
>> I used sbuild:
>> [1]: sbuild --extra-repository='deb http://deb.debian.org/debian
>> experimental main' --build-dep-resolver=aptitude
>>
>> Directly using it returns the same log for me, i.e. test failures. These
>> are the steps I took:
>>
>> * In node-gyp, pass in nodejs(>= 12) and libnode-dev(>= 12) in d/control.
>> Build it with the sbuild command[1] above [so as to ensure getting the deb
>> with nodejs-12]
>> * In node-nan, pass in nodejs(>= 12) in d/control and use the same
>> command with extra-package i.e.: [since node-gyp is a reverse-build-dep]
>>
>> sbuild --extra-repository='deb http://deb.debian.org/debian experimental
>> main' --build-dep-resolver=aptitude
>> --extra-package='/home/nilesh/gyp/node-gyp_6.0.1-2_all.deb'
>>
>> Does it not seem right to you? Or am I missing something?
>>
>
> I didn't mention it completely. After taking those steps, it still doesn't
> work and returns the same logs as I pasted earlier.
>

The problem is the "build-dep-resolver" here.

Jérémy
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] nodejs-12 transition

[Nilesh Patra]

On Sun, 19 Jan 2020, 01:31 Nilesh Patra,  wrote:

>
>
> On Sat, 18 Jan 2020 at 13:33, Jérémy Lal  wrote:
>
>> Nilesh: how to you build node-nan ?
>> Using
>> gbp buildpackage -d experimental --extra-repository='deb
>> http://httpredir.debian.org/debian experimental main'
>> --build-dep-resolver=aspcud
>> tests + autopkgtests are all right doing that.
>>
>
> Hi,
> I used sbuild:
> [1]: sbuild --extra-repository='deb http://deb.debian.org/debian
> experimental main' --build-dep-resolver=aptitude
>
> Directly using it returns the same log for me, i.e. test failures. These
> are the steps I took:
>
> * In node-gyp, pass in nodejs(>= 12) and libnode-dev(>= 12) in d/control.
> Build it with the sbuild command[1] above [so as to ensure getting the deb
> with nodejs-12]
> * In node-nan, pass in nodejs(>= 12) in d/control and use the same command
> with extra-package i.e.: [since node-gyp is a reverse-build-dep]
>
> sbuild --extra-repository='deb http://deb.debian.org/debian experimental
> main' --build-dep-resolver=aptitude
> --extra-package='/home/nilesh/gyp/node-gyp_6.0.1-2_all.deb'
>
> Does it not seem right to you? Or am I missing something?
>

I didn't mention it completely. After taking those steps, it still doesn't
work and returns the same logs as I pasted earlier.

>
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] nodejs-12 transition

[Nilesh Patra]

On Sat, 18 Jan 2020 at 13:33, Jérémy Lal  wrote:

> Nilesh: how to you build node-nan ?
> Using
> gbp buildpackage -d experimental --extra-repository='deb
> http://httpredir.debian.org/debian experimental main'
> --build-dep-resolver=aspcud
> tests + autopkgtests are all right doing that.
>

Hi,
I used sbuild:
[1]: sbuild --extra-repository='deb http://deb.debian.org/debian
experimental main' --build-dep-resolver=aptitude

Directly using it returns the same log for me, i.e. test failures. These
are the steps I took:

* In node-gyp, pass in nodejs(>= 12) and libnode-dev(>= 12) in d/control.
Build it with the sbuild command[1] above [so as to ensure getting the deb
with nodejs-12]
* In node-nan, pass in nodejs(>= 12) in d/control and use the same command
with extra-package i.e.: [since node-gyp is a reverse-build-dep]

sbuild --extra-repository='deb http://deb.debian.org/debian experimental
main' --build-dep-resolver=aptitude
--extra-package='/home/nilesh/gyp/node-gyp_6.0.1-2_all.deb'

Does it not seem right to you? Or am I missing something?
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] nodejs-12 transition

[Jérémy Lal]

Nilesh: how to you build node-nan ?
Using
gbp buildpackage -d experimental --extra-repository='deb
http://httpredir.debian.org/debian experimental main'
--build-dep-resolver=aspcud
tests + autopkgtests are all right doing that.


Le sam. 18 janv. 2020 à 20:08, Jérémy Lal  a écrit :

> Nilesh,
> i'm having a look at node-gyp/nan.
>
> Le sam. 18 janv. 2020 à 20:04, Nilesh Patra  a
> écrit :
>
>>
>>
>> On Sat, 18 Jan 2020 at 01:06, Xavier  wrote:
>>
>>> Le 17/01/2020 à 18:55, Nilesh Patra a écrit :
>>> >
>>> > On Fri, 17 Jan 2020 at 05:02, Pirate Praveen >> > > wrote:
>>> >
>>> > On വെ, Jan 17, 2020 at 07:33, Paolo Greppi >> > >
>>> > wrote:
>>> > > Il 16/01/20 20:35, Pirate Praveen ha scritto:
>>> > >>
>>> > >>
>>> > >>  On വ്യാ, Jan 16, 2020 at 13:27, Nilesh Patra
>>> > >> mailto:npatra...@gmail.com>> wrote:
>>> > >>>  Hi,
>>> > >>>  I had been lately seeing discussions in the list regarding
>>> > >>> requiring transition for nodejs-12 to unstable. I tested all
>>> the
>>> > >>> reverse depends and this is the list of all failing
>>> > >>> reverse-depends[1] and the repository[2] contains all the
>>> > >>> individual logs(for all reverse-depends) for convenience.
>>> > >>>  Also rebuilt the reverse-build-depends and this[3] is the
>>> list of
>>> > >>> depends that fail and the individual logs are in the same
>>> > >>> repository[4]
>>> > >>>
>>> > >>>  [1];
>>> > >>>
>>> >
>>> https://git.fosscommunity.in/gi-boi/nodejs_autopkgtest_results/blob/master/rdeps
>>> > >>>  [2]:
>>> > >>>
>>> https://git.fosscommunity.in/gi-boi/nodejs_autopkgtest_results/
>>> > >>>  [3]:
>>> > >>>
>>> >
>>> https://git.fosscommunity.in/gi-boi/nodejs_rebuild_results/blob/master/rebuild_deps
>>> > >>>  [4]:
>>> https://git.fosscommunity.in/gi-boi/nodejs_rebuild_results/
>>> > >>>
>>> >
>>> > [..]
>>> >
>>> > >>  Thanks a lot Nilesh for doing it. This is really helpful.
>>> > >>  Some the failures may be unrelated to nodejs 12 change, for
>>> example
>>> > >>  https://tracker.debian.org/pkg/node-dagre-layout this is
>>> already
>>> > >> failing (I think thanks to /usr/lib to /usr/share migration).
>>> > >> Similarly for autopkgtest. So among the packages that failed, we
>>> > >> need to find out which of them are already failing (we can get
>>> this
>>> > >> information from tracker.debian.org >> >).
>>> > >>
>>> > >>>  Thanks and Regards
>>> > >>>  Nilesh
>>> > >
>>> > > Hi Nilesh and thanks for the good work.
>>> > >
>>> > > For nodejs_autopkgtest_results, of the 1288 logs only 74 contain
>>> the
>>> > > string 'FAIL non-zero exit status' (see attached
>>> > > nodejs_autopkgtest_results-failed).
>>> > > I propose to mass-file bugs against each of them for easier
>>> tracking.
>>> >
>>> > I think a wiki page might be simpler at least for first pass.
>>> > See transition of rails 5 for example
>>> >
>>> https://salsa.debian.org/ruby-team/rails/-/wikis/Transition-to-Rails-5.2-for-Debian-Buster
>>> >
>>> > For packaes that can't be fixed easily we can file bugs.
>>> >
>>> > > For nodejs_rebuild_results, of the 1168 logs only the 62 in the
>>> > > rebdeps file actually failed.
>>> > > Some may be false positives as suggested by Praveen; had you used
>>> > > ratt [1] you could have told it to retry the failing builds
>>> without
>>> > > the new package (in this case nodejs 12), this would exclude
>>> most of
>>> > > those that are already failing.
>>> > > Who feels like doing it manually now for the 62 failing builds ?
>>> >
>>> > >
>>> > Once we have wiki, people can take ownership of a subset and look
>>> at
>>> > specific packages (dividing the whole work).
>>> >
>>> >
>>> > I have created the wiki page here[1] with relevant reverse and reverse
>>> > build depends. Updated the autopkgtest failures as per Paolo's list(74
>>> > in number). The logs are available for individual logs for convenience
>>> > as well.(marked the mail containing links above)
>>> >
>>> > [1]:
>>> >
>>> https://salsa.debian.org/js-team/nodejs/-/wikis/Transition-to-Nodejs-12-for-Debian-Unstable
>>> >
>>> > Thanks and Regards
>>> > Nilesh
>>>
>>> Hi,
>>>
>>> node-tap is ready, was just an output problem. (I forgot to bring my
>>> Yubikey, then I'm unable to push it for now. NB: can be pushed directly
>>> to unstable: just 3 tests disabled)
>>>
>>> Cheers,
>>> Xavier
>>>
>>
>> Hi,
>>
>> I was trying to fix node-node-sass to build with nodejs-12. In order to
>> do that, I first needed to build node-gyp and node-nan, (both native
>> package and node-node-sass's build-deps) with nodejs-12. While building
>> node-nan with nodejs-12 (and with node-gyp as --extra-package since it is
>> node-nan's build-dep), I encounter several of these:
>>
>>   42) 

Re: [Pkg-javascript-devel] nodejs-12 transition

[Jérémy Lal]

Nilesh,
i'm having a look at node-gyp/nan.

Le sam. 18 janv. 2020 à 20:04, Nilesh Patra  a écrit :

>
>
> On Sat, 18 Jan 2020 at 01:06, Xavier  wrote:
>
>> Le 17/01/2020 à 18:55, Nilesh Patra a écrit :
>> >
>> > On Fri, 17 Jan 2020 at 05:02, Pirate Praveen > > > wrote:
>> >
>> > On വെ, Jan 17, 2020 at 07:33, Paolo Greppi > > >
>> > wrote:
>> > > Il 16/01/20 20:35, Pirate Praveen ha scritto:
>> > >>
>> > >>
>> > >>  On വ്യാ, Jan 16, 2020 at 13:27, Nilesh Patra
>> > >> mailto:npatra...@gmail.com>> wrote:
>> > >>>  Hi,
>> > >>>  I had been lately seeing discussions in the list regarding
>> > >>> requiring transition for nodejs-12 to unstable. I tested all the
>> > >>> reverse depends and this is the list of all failing
>> > >>> reverse-depends[1] and the repository[2] contains all the
>> > >>> individual logs(for all reverse-depends) for convenience.
>> > >>>  Also rebuilt the reverse-build-depends and this[3] is the list
>> of
>> > >>> depends that fail and the individual logs are in the same
>> > >>> repository[4]
>> > >>>
>> > >>>  [1];
>> > >>>
>> >
>> https://git.fosscommunity.in/gi-boi/nodejs_autopkgtest_results/blob/master/rdeps
>> > >>>  [2]:
>> > >>> https://git.fosscommunity.in/gi-boi/nodejs_autopkgtest_results/
>> > >>>  [3]:
>> > >>>
>> >
>> https://git.fosscommunity.in/gi-boi/nodejs_rebuild_results/blob/master/rebuild_deps
>> > >>>  [4]:
>> https://git.fosscommunity.in/gi-boi/nodejs_rebuild_results/
>> > >>>
>> >
>> > [..]
>> >
>> > >>  Thanks a lot Nilesh for doing it. This is really helpful.
>> > >>  Some the failures may be unrelated to nodejs 12 change, for
>> example
>> > >>  https://tracker.debian.org/pkg/node-dagre-layout this is
>> already
>> > >> failing (I think thanks to /usr/lib to /usr/share migration).
>> > >> Similarly for autopkgtest. So among the packages that failed, we
>> > >> need to find out which of them are already failing (we can get
>> this
>> > >> information from tracker.debian.org > >).
>> > >>
>> > >>>  Thanks and Regards
>> > >>>  Nilesh
>> > >
>> > > Hi Nilesh and thanks for the good work.
>> > >
>> > > For nodejs_autopkgtest_results, of the 1288 logs only 74 contain
>> the
>> > > string 'FAIL non-zero exit status' (see attached
>> > > nodejs_autopkgtest_results-failed).
>> > > I propose to mass-file bugs against each of them for easier
>> tracking.
>> >
>> > I think a wiki page might be simpler at least for first pass.
>> > See transition of rails 5 for example
>> >
>> https://salsa.debian.org/ruby-team/rails/-/wikis/Transition-to-Rails-5.2-for-Debian-Buster
>> >
>> > For packaes that can't be fixed easily we can file bugs.
>> >
>> > > For nodejs_rebuild_results, of the 1168 logs only the 62 in the
>> > > rebdeps file actually failed.
>> > > Some may be false positives as suggested by Praveen; had you used
>> > > ratt [1] you could have told it to retry the failing builds
>> without
>> > > the new package (in this case nodejs 12), this would exclude most
>> of
>> > > those that are already failing.
>> > > Who feels like doing it manually now for the 62 failing builds ?
>> >
>> > >
>> > Once we have wiki, people can take ownership of a subset and look at
>> > specific packages (dividing the whole work).
>> >
>> >
>> > I have created the wiki page here[1] with relevant reverse and reverse
>> > build depends. Updated the autopkgtest failures as per Paolo's list(74
>> > in number). The logs are available for individual logs for convenience
>> > as well.(marked the mail containing links above)
>> >
>> > [1]:
>> >
>> https://salsa.debian.org/js-team/nodejs/-/wikis/Transition-to-Nodejs-12-for-Debian-Unstable
>> >
>> > Thanks and Regards
>> > Nilesh
>>
>> Hi,
>>
>> node-tap is ready, was just an output problem. (I forgot to bring my
>> Yubikey, then I'm unable to push it for now. NB: can be pushed directly
>> to unstable: just 3 tests disabled)
>>
>> Cheers,
>> Xavier
>>
>
> Hi,
>
> I was trying to fix node-node-sass to build with nodejs-12. In order to do
> that, I first needed to build node-gyp and node-nan, (both native package
> and node-node-sass's build-deps) with nodejs-12. While building node-nan
> with nodejs-12 (and with node-gyp as --extra-package since it is node-nan's
> build-dep), I encounter several of these:
>
>   42) test/js/typedarrays-test.js
> Error: The module '/<>/test/build/Release/weak2.node'
> was compiled against a different Node.js version using
> NODE_MODULE_VERSION 64. This version of Node.js requires
> NODE_MODULE_VERSION 72. Please try re-compiling or re-installing
> the module (for instance, using `npm rebuild` or `npm install`).
> at Object.Module._extensions..node 
> (internal/modules/cjs/loader.js:1025:18)
> at 

Re: [Pkg-javascript-devel] nodejs-12 transition

[Nilesh Patra]

On Sat, 18 Jan 2020 at 01:06, Xavier  wrote:

> Le 17/01/2020 à 18:55, Nilesh Patra a écrit :
> >
> > On Fri, 17 Jan 2020 at 05:02, Pirate Praveen  > > wrote:
> >
> > On വെ, Jan 17, 2020 at 07:33, Paolo Greppi  > >
> > wrote:
> > > Il 16/01/20 20:35, Pirate Praveen ha scritto:
> > >>
> > >>
> > >>  On വ്യാ, Jan 16, 2020 at 13:27, Nilesh Patra
> > >> mailto:npatra...@gmail.com>> wrote:
> > >>>  Hi,
> > >>>  I had been lately seeing discussions in the list regarding
> > >>> requiring transition for nodejs-12 to unstable. I tested all the
> > >>> reverse depends and this is the list of all failing
> > >>> reverse-depends[1] and the repository[2] contains all the
> > >>> individual logs(for all reverse-depends) for convenience.
> > >>>  Also rebuilt the reverse-build-depends and this[3] is the list
> of
> > >>> depends that fail and the individual logs are in the same
> > >>> repository[4]
> > >>>
> > >>>  [1];
> > >>>
> >
> https://git.fosscommunity.in/gi-boi/nodejs_autopkgtest_results/blob/master/rdeps
> > >>>  [2]:
> > >>> https://git.fosscommunity.in/gi-boi/nodejs_autopkgtest_results/
> > >>>  [3]:
> > >>>
> >
> https://git.fosscommunity.in/gi-boi/nodejs_rebuild_results/blob/master/rebuild_deps
> > >>>  [4]:
> https://git.fosscommunity.in/gi-boi/nodejs_rebuild_results/
> > >>>
> >
> > [..]
> >
> > >>  Thanks a lot Nilesh for doing it. This is really helpful.
> > >>  Some the failures may be unrelated to nodejs 12 change, for
> example
> > >>  https://tracker.debian.org/pkg/node-dagre-layout this is already
> > >> failing (I think thanks to /usr/lib to /usr/share migration).
> > >> Similarly for autopkgtest. So among the packages that failed, we
> > >> need to find out which of them are already failing (we can get
> this
> > >> information from tracker.debian.org ).
> > >>
> > >>>  Thanks and Regards
> > >>>  Nilesh
> > >
> > > Hi Nilesh and thanks for the good work.
> > >
> > > For nodejs_autopkgtest_results, of the 1288 logs only 74 contain
> the
> > > string 'FAIL non-zero exit status' (see attached
> > > nodejs_autopkgtest_results-failed).
> > > I propose to mass-file bugs against each of them for easier
> tracking.
> >
> > I think a wiki page might be simpler at least for first pass.
> > See transition of rails 5 for example
> >
> https://salsa.debian.org/ruby-team/rails/-/wikis/Transition-to-Rails-5.2-for-Debian-Buster
> >
> > For packaes that can't be fixed easily we can file bugs.
> >
> > > For nodejs_rebuild_results, of the 1168 logs only the 62 in the
> > > rebdeps file actually failed.
> > > Some may be false positives as suggested by Praveen; had you used
> > > ratt [1] you could have told it to retry the failing builds without
> > > the new package (in this case nodejs 12), this would exclude most
> of
> > > those that are already failing.
> > > Who feels like doing it manually now for the 62 failing builds ?
> >
> > >
> > Once we have wiki, people can take ownership of a subset and look at
> > specific packages (dividing the whole work).
> >
> >
> > I have created the wiki page here[1] with relevant reverse and reverse
> > build depends. Updated the autopkgtest failures as per Paolo's list(74
> > in number). The logs are available for individual logs for convenience
> > as well.(marked the mail containing links above)
> >
> > [1]:
> >
> https://salsa.debian.org/js-team/nodejs/-/wikis/Transition-to-Nodejs-12-for-Debian-Unstable
> >
> > Thanks and Regards
> > Nilesh
>
> Hi,
>
> node-tap is ready, was just an output problem. (I forgot to bring my
> Yubikey, then I'm unable to push it for now. NB: can be pushed directly
> to unstable: just 3 tests disabled)
>
> Cheers,
> Xavier
>

Hi,

I was trying to fix node-node-sass to build with nodejs-12. In order to do
that, I first needed to build node-gyp and node-nan, (both native package
and node-node-sass's build-deps) with nodejs-12. While building node-nan
with nodejs-12 (and with node-gyp as --extra-package since it is node-nan's
build-dep), I encounter several of these:

  42) test/js/typedarrays-test.js
Error: The module '/<>/test/build/Release/weak2.node'
was compiled against a different Node.js version using
NODE_MODULE_VERSION 64. This version of Node.js requires
NODE_MODULE_VERSION 72. Please try re-compiling or re-installing
the module (for instance, using `npm rebuild` or `npm install`).
at Object.Module._extensions..node (internal/modules/cjs/loader.js:1025:18)
at Module.load (internal/modules/cjs/loader.js:815:32)
at Function.Module._load (internal/modules/cjs/loader.js:727:14)
at Module.require (internal/modules/cjs/loader.js:852:19)
at require (internal/modules/cjs/helpers.js:74:18)
at bindings 

Re: [Pkg-javascript-devel] nodejs-12 transition

[Jérémy Lal]

Le ven. 17 janv. 2020 à 19:19, Nilesh Patra  a écrit :

>
>
> On Fri, 17 Jan 2020 at 05:02, Pirate Praveen 
> wrote:
>
>>
>>
>> On വെ, Jan 17, 2020 at 07:33, Paolo Greppi 
>> wrote:
>> > Il 16/01/20 20:35, Pirate Praveen ha scritto:
>> >>
>> >>
>> >>  On വ്യാ, Jan 16, 2020 at 13:27, Nilesh Patra
>> >>  wrote:
>> >>>  Hi,
>> >>>  I had been lately seeing discussions in the list regarding
>> >>> requiring transition for nodejs-12 to unstable. I tested all the
>> >>> reverse depends and this is the list of all failing
>> >>> reverse-depends[1] and the repository[2] contains all the
>> >>> individual logs(for all reverse-depends) for convenience.
>> >>>  Also rebuilt the reverse-build-depends and this[3] is the list of
>> >>> depends that fail and the individual logs are in the same
>> >>> repository[4]
>> >>>
>> >>>  [1];
>> >>>
>> https://git.fosscommunity.in/gi-boi/nodejs_autopkgtest_results/blob/master/rdeps
>> >>>  [2]:
>> >>> https://git.fosscommunity.in/gi-boi/nodejs_autopkgtest_results/
>> >>>  [3]:
>> >>>
>> https://git.fosscommunity.in/gi-boi/nodejs_rebuild_results/blob/master/rebuild_deps
>> >>>  [4]: https://git.fosscommunity.in/gi-boi/nodejs_rebuild_results/
>> >>>
>>
>
> [..]
>
> >>  Thanks a lot Nilesh for doing it. This is really helpful.
>> >>  Some the failures may be unrelated to nodejs 12 change, for example
>> >>  https://tracker.debian.org/pkg/node-dagre-layout this is already
>> >> failing (I think thanks to /usr/lib to /usr/share migration).
>> >> Similarly for autopkgtest. So among the packages that failed, we
>> >> need to find out which of them are already failing (we can get this
>> >> information from tracker.debian.org).
>> >>
>> >>>  Thanks and Regards
>> >>>  Nilesh
>> >
>> > Hi Nilesh and thanks for the good work.
>> >
>> > For nodejs_autopkgtest_results, of the 1288 logs only 74 contain the
>> > string 'FAIL non-zero exit status' (see attached
>> > nodejs_autopkgtest_results-failed).
>> > I propose to mass-file bugs against each of them for easier tracking.
>>
>> I think a wiki page might be simpler at least for first pass.
>> See transition of rails 5 for example
>>
>> https://salsa.debian.org/ruby-team/rails/-/wikis/Transition-to-Rails-5.2-for-Debian-Buster
>>
>> For packaes that can't be fixed easily we can file bugs.
>>
>> > For nodejs_rebuild_results, of the 1168 logs only the 62 in the
>> > rebdeps file actually failed.
>> > Some may be false positives as suggested by Praveen; had you used
>> > ratt [1] you could have told it to retry the failing builds without
>> > the new package (in this case nodejs 12), this would exclude most of
>> > those that are already failing.
>> > Who feels like doing it manually now for the 62 failing builds ?
>>
>> >
>> Once we have wiki, people can take ownership of a subset and look at
>> specific packages (dividing the whole work).
>>
>>
> I have created the wiki page here[1] with relevant reverse and reverse
> build depends. Updated the autopkgtest failures as per Paolo's list(74 in
> number). The logs are available for individual logs for convenience as
> well.(marked the mail containing links above)
>
> [1]:
> https://salsa.debian.org/js-team/nodejs/-/wikis/Transition-to-Nodejs-12-for-Debian-Unstable
>

Thanks a lot.

I'll try to help with the c++ addons.

Jérémy
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] nodejs-12 transition

[Nilesh Patra]

On Fri, 17 Jan 2020 at 05:02, Pirate Praveen 
wrote:

>
>
> On വെ, Jan 17, 2020 at 07:33, Paolo Greppi 
> wrote:
> > Il 16/01/20 20:35, Pirate Praveen ha scritto:
> >>
> >>
> >>  On വ്യാ, Jan 16, 2020 at 13:27, Nilesh Patra
> >>  wrote:
> >>>  Hi,
> >>>  I had been lately seeing discussions in the list regarding
> >>> requiring transition for nodejs-12 to unstable. I tested all the
> >>> reverse depends and this is the list of all failing
> >>> reverse-depends[1] and the repository[2] contains all the
> >>> individual logs(for all reverse-depends) for convenience.
> >>>  Also rebuilt the reverse-build-depends and this[3] is the list of
> >>> depends that fail and the individual logs are in the same
> >>> repository[4]
> >>>
> >>>  [1];
> >>>
> https://git.fosscommunity.in/gi-boi/nodejs_autopkgtest_results/blob/master/rdeps
> >>>  [2]:
> >>> https://git.fosscommunity.in/gi-boi/nodejs_autopkgtest_results/
> >>>  [3]:
> >>>
> https://git.fosscommunity.in/gi-boi/nodejs_rebuild_results/blob/master/rebuild_deps
> >>>  [4]: https://git.fosscommunity.in/gi-boi/nodejs_rebuild_results/
> >>>
>

[..]

>>  Thanks a lot Nilesh for doing it. This is really helpful.
> >>  Some the failures may be unrelated to nodejs 12 change, for example
> >>  https://tracker.debian.org/pkg/node-dagre-layout this is already
> >> failing (I think thanks to /usr/lib to /usr/share migration).
> >> Similarly for autopkgtest. So among the packages that failed, we
> >> need to find out which of them are already failing (we can get this
> >> information from tracker.debian.org).
> >>
> >>>  Thanks and Regards
> >>>  Nilesh
> >
> > Hi Nilesh and thanks for the good work.
> >
> > For nodejs_autopkgtest_results, of the 1288 logs only 74 contain the
> > string 'FAIL non-zero exit status' (see attached
> > nodejs_autopkgtest_results-failed).
> > I propose to mass-file bugs against each of them for easier tracking.
>
> I think a wiki page might be simpler at least for first pass.
> See transition of rails 5 for example
>
> https://salsa.debian.org/ruby-team/rails/-/wikis/Transition-to-Rails-5.2-for-Debian-Buster
>
> For packaes that can't be fixed easily we can file bugs.
>
> > For nodejs_rebuild_results, of the 1168 logs only the 62 in the
> > rebdeps file actually failed.
> > Some may be false positives as suggested by Praveen; had you used
> > ratt [1] you could have told it to retry the failing builds without
> > the new package (in this case nodejs 12), this would exclude most of
> > those that are already failing.
> > Who feels like doing it manually now for the 62 failing builds ?
>
> >
> Once we have wiki, people can take ownership of a subset and look at
> specific packages (dividing the whole work).
>
>
I have created the wiki page here[1] with relevant reverse and reverse
build depends. Updated the autopkgtest failures as per Paolo's list(74 in
number). The logs are available for individual logs for convenience as
well.(marked the mail containing links above)

[1]:
https://salsa.debian.org/js-team/nodejs/-/wikis/Transition-to-Nodejs-12-for-Debian-Unstable

Thanks and Regards
Nilesh
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] nodejs-12 transition

[Pirate Praveen]

On വെ, Jan 17, 2020 at 07:33, Paolo Greppi  
wrote:

Il 16/01/20 20:35, Pirate Praveen ha scritto:



 On വ്യാ, Jan 16, 2020 at 13:27, Nilesh Patra 
 wrote:

 Hi,
 I had been lately seeing discussions in the list regarding 
requiring transition for nodejs-12 to unstable. I tested all the 
reverse depends and this is the list of all failing 
reverse-depends[1] and the repository[2] contains all the 
individual logs(for all reverse-depends) for convenience.
 Also rebuilt the reverse-build-depends and this[3] is the list of 
depends that fail and the individual logs are in the same 
repository[4]


 [1]; 
https://git.fosscommunity.in/gi-boi/nodejs_autopkgtest_results/blob/master/rdeps
 [2]: 
https://git.fosscommunity.in/gi-boi/nodejs_autopkgtest_results/
 [3]: 
https://git.fosscommunity.in/gi-boi/nodejs_rebuild_results/blob/master/rebuild_deps

 [4]: https://git.fosscommunity.in/gi-boi/nodejs_rebuild_results/



 Thanks a lot Nilesh for doing it. This is really helpful.
 Some the failures may be unrelated to nodejs 12 change, for example 
 https://tracker.debian.org/pkg/node-dagre-layout this is already 
failing (I think thanks to /usr/lib to /usr/share migration). 
Similarly for autopkgtest. So among the packages that failed, we 
need to find out which of them are already failing (we can get this 
information from tracker.debian.org).



 Thanks and Regards
 Nilesh


Hi Nilesh and thanks for the good work.

For nodejs_autopkgtest_results, of the 1288 logs only 74 contain the 
string 'FAIL non-zero exit status' (see attached 
nodejs_autopkgtest_results-failed).

I propose to mass-file bugs against each of them for easier tracking.


I think a wiki page might be simpler at least for first pass.
See transition of rails 5 for example 
https://salsa.debian.org/ruby-team/rails/-/wikis/Transition-to-Rails-5.2-for-Debian-Buster


For packaes that can't be fixed easily we can file bugs.

For nodejs_rebuild_results, of the 1168 logs only the 62 in the 
rebdeps file actually failed.
Some may be false positives as suggested by Praveen; had you used 
ratt [1] you could have told it to retry the failing builds without 
the new package (in this case nodejs 12), this would exclude most of 
those that are already failing.

Who feels like doing it manually now for the 62 failing builds ?




Once we have wiki, people can take ownership of a subset and look at 
specific packages (dividing the whole work).




--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] nodejs-12 transition

[Paolo Greppi]

Il 16/01/20 20:35, Pirate Praveen ha scritto:
> 
> 
> On വ്യാ, Jan 16, 2020 at 13:27, Nilesh Patra  wrote:
>> Hi,
>> I had been lately seeing discussions in the list regarding requiring 
>> transition for nodejs-12 to unstable. I tested all the reverse depends and 
>> this is the list of all failing reverse-depends[1] and the repository[2] 
>> contains all the individual logs(for all reverse-depends) for convenience.
>> Also rebuilt the reverse-build-depends and this[3] is the list of depends 
>> that fail and the individual logs are in the same repository[4]
>>
>> [1]; 
>> https://git.fosscommunity.in/gi-boi/nodejs_autopkgtest_results/blob/master/rdeps
>> [2]: https://git.fosscommunity.in/gi-boi/nodejs_autopkgtest_results/
>> [3]: 
>> https://git.fosscommunity.in/gi-boi/nodejs_rebuild_results/blob/master/rebuild_deps
>> [4]: https://git.fosscommunity.in/gi-boi/nodejs_rebuild_results/
>>
> 
> Thanks a lot Nilesh for doing it. This is really helpful.
> Some the failures may be unrelated to nodejs 12 change, for example  
> https://tracker.debian.org/pkg/node-dagre-layout this is already failing (I 
> think thanks to /usr/lib to /usr/share migration). Similarly for autopkgtest. 
> So among the packages that failed, we need to find out which of them are 
> already failing (we can get this information from tracker.debian.org).
> 
>> Thanks and Regards
>> Nilesh

Hi Nilesh and thanks for the good work.

For nodejs_autopkgtest_results, of the 1288 logs only 74 contain the string 
'FAIL non-zero exit status' (see attached nodejs_autopkgtest_results-failed).
I propose to mass-file bugs against each of them for easier tracking.

For nodejs_rebuild_results, of the 1168 logs only the 62 in the rebdeps file 
actually failed.
Some may be false positives as suggested by Praveen; had you used ratt [1] you 
could have told it to retry the failing builds without the new package (in this 
case nodejs 12), this would exclude most of those that are already failing.
Who feels like doing it manually now for the 62 failing builds ?

Paolo

[1] https://github.com/Debian/ratt
acorn.log
babel-minify.log
html2canvas.log
node-babel-plugin-transform-define.log
node-body-parser.log
node-cacache.log
node-chokidar.log
node-copy-webpack-plugin.log
node-diffie-hellman.log
node-diff.log
node-ebnf-parser.log
node-eslint-plugin-flowtype.log
node-eslint-plugin-html.log
node-expat.log
node-express.log
node-extend-shallow.log
node-grunt-babel.log
node-grunt-contrib-nodeunit.log
node-grunt-legacy-util.log
node-grunt-webpack.log
node-iconv-lite.log
node-iconv.log
node-immutable-tuple.log
node-jquery-textcomplete.log
node-jquery.waitforimages.log
node-klaw.log
node-leaflet-formbuilder.log
node-leaflet-hash.log
node-leveldown.log
node-levn.log
node-libnpx.log
node-lockfile.log
node-mapnik.log
node-millstone.log
node-multiparty.log
node-nodedbi.log
node-node-localstorage.log
node-node-sass.log
node-npm-bundled.log
node-npmrc.log
node-optionator.log
node-pako.log
node-rai.log
node-raw-body.log
node-re2.log
node-request-promise.log
node-serve-index.log
node-shell-quote.log
node-shiny-server-client.log
node-simplesmtp.log
node-sinon-chai.log
node-source-map-support.log
node-sqlite3.log
node-srs.log
node-sshpk.log
node-stack-utils.log
node-stream-splicer.log
node-string-decoder.log
node-stringprep.log
node-superagent.log
node-supertest.log
node-tap.log
node-telegram-bot-api.log
node-tmp.log
node-to-fast-properties.log
node-type-check.log
node-uniq.log
node-unique-filename.log
node-vinyl-fs.log
node-vue-template-compiler.log
node-websocket.log
node-xmpp.log
node-xoauth2.log
node-zipfile.log
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] nodejs-12 transition

[Pirate Praveen]

On വ്യാ, Jan 16, 2020 at 13:27, Nilesh Patra 
 wrote:

Hi,
I had been lately seeing discussions in the list regarding requiring 
transition for nodejs-12 to unstable. I tested all the reverse 
depends and this is the list of all failing reverse-depends[1] and 
the repository[2] contains all the individual logs(for all 
reverse-depends) for convenience.
Also rebuilt the reverse-build-depends and this[3] is the list of 
depends that fail and the individual logs are in the same 
repository[4]


[1]; 
https://git.fosscommunity.in/gi-boi/nodejs_autopkgtest_results/blob/master/rdeps

[2]: https://git.fosscommunity.in/gi-boi/nodejs_autopkgtest_results/
[3]: 
https://git.fosscommunity.in/gi-boi/nodejs_rebuild_results/blob/master/rebuild_deps

[4]: https://git.fosscommunity.in/gi-boi/nodejs_rebuild_results/



Thanks a lot Nilesh for doing it. This is really helpful.
Some the failures may be unrelated to nodejs 12 change, for example  
https://tracker.debian.org/pkg/node-dagre-layout this is already 
failing (I think thanks to /usr/lib to /usr/share migration). Similarly 
for autopkgtest. So among the packages that failed, we need to find out 
which of them are already failing (we can get this information from 
tracker.debian.org).



Thanks and Regards
Nilesh




--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel