[Pkg-javascript-devel] nodejs-12 transition

[Pirate Praveen]

On Sun, Mar 8, 2020 at 10:50 am, Jérémy Lal <kapouer at melix.org> wrote:
> 
> 
> Le dim. 8 mars 2020 à 06:04, Pirate Praveen 
> <praveen at onenetbeyond.org> a écrit :
>> 
>> 
>>  On 2020, മാർച്ച് 7 2:34:17 PM IST, "Jérémy Lal" 
>> <kapouer at melix.org> wrote:
>>  >Le sam. 7 mars 2020 à 06:18, Nilesh Patra <npatra974 at 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.
>> 
>>  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.