[Pkg-javascript-devel] acorn 8

[Xavier]

Le 09/10/2020 à 17:51, Xavier a écrit :
> Le 09/10/2020 à 15:42, Xavier a écrit :
>> Le 09/10/2020 à 11:55, Xavier a écrit :
>>> Le 08/10/2020 à 11:42, Jonas Smedegaard a écrit :
>>>> Quoting Xavier (2020-10-08 06:13:30)
>>>>> Le 07/10/2020 à 17:13, Xavier a écrit :
>>>>>> Le 07/10/2020 à 17:03, Carsten Schoenert a écrit :
>>>>>>> Hello Xavier,
>>>>>>>
>>>>>>> Am 07.10.20 um 16:29 schrieb Xavier:
>>>>>>>> Le 07/10/2020 à 10:29, Carsten Schoenert a écrit :
>>>>>>>> this modules looks useless in Debian:
>>>>>>>>  * no reverse-dependencies
>>>>>>>
>>>>>>> well, might simply because the version in Debian is far to old for 
>>>>>>> all possibly other packages. ;) I haven't looked at packages that 
>>>>>>> using now preshipped pdf.js.
>>>>>>>
>>>>>>>>  * one binary mas to be removed (xul component, #906835)
>>>>>>>
>>>>>>> Yes, obviously.
>>>>>>>
>>>>>>>>  * you're the first person who looks to it for a while ;-)
>>>>>>>>
>>>>>>>> Then do you need its update ? I can do it but it requires some 
>>>>>>>> work (zelenka.debian.org is working on it :-D).
>>>>>>>
>>>>>>> No hurry, I was today looking into upgrading kopano-webapp to 4.3 
>>>>>>> and the Kopano is using pdf.js since version 4.0 here.
>>>>>>>
>>>>>>> There are other issues to solve, but using pdf.js from Debian would 
>>>>>>> prevent the requirement to use the embedded version.
>>>>>>
>>>>>> OK, I'll update it
>>>>>
>>>>> Sadly updating pdf.js requires to update acorn to acorn 7.4. This will
>>>>> take time...
>>>>
>>>> Perhaps then sensible to update it to something newer yet not newest.
>>>
>>> Finally it seems easy to upgrade acorn (with recent rollup* upgrades). I
>>> pushed my work to experimental.
>>>
>>> The only problem I found with this upgrade is related to rollup build
>>> (not fixed for now).
>>
>> Mmm, Ruby-Team's tool didn't find all reverse deps (due to its multiple
>> package names...). Most package succeeds but it seems to be a problem
>> with acorn-walk:
>>
>>  * rollup fails to build with:
>>
>>   Error: 'walk' is not exported by
>>   ../../../usr/share/nodejs/estree-walker/index.js
> 
> Unable to fix this for now...
> 
>>  * node-promise:
>>
>>   Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './dist/walk'
>>   is not defined by "exports" in
>>   /usr/share/nodejs/acorn-walk/package.json
> 
> node-promise require acorn ^1.0 ! Seems easy to fix

Hi,

I fixed node-promise and rollup. Now acorn 8 seems ready for unstable.

Unless someone disagrees, I'm planing to push it to unstable.

However, our usage of virtual names in build dependencies make dak
blind: only 2 packages (rollup and babel8) use the real package name
(node-debbundle-acorn). Others use one of its virtual names, then all
Debian tools can't find real reverse dependencies (ruby-team/meta, dak,
reverse-depends,...). So I'd like to add this in our policy: "never use
a virtual dependency in build dependencies unless it is known by cme".

What do you think ?

NB: dh-sequence-nodejs is going to be known by cme (#971784)