Le 25/02/2020 à 22:19, Jonas Smedegaard a écrit : > Quoting Bastien ROUCARIES (2020-02-25 21:13:48) >> Le mar. 25 févr. 2020 à 19:48, Jonas Smedegaard <jo...@jones.dk> a écrit : >> >>> control: reassign -1 node-espree >>> control: affects -1 node-eslint-scope >>> >>> Quoting Xavier (2020-02-25 18:29:35) >>>> Le 23/02/2020 à 14:50, Lucas Nussbaum a écrit : >>>>> During a rebuild of all packages in sid, your package failed to >>>>> build on amd64. >>>> >>>> Some test are incompatible with node-espree-6. The fix could be >>>> simply: >>> >>> Certainly not a fix to disable tests. >>> >>> The package node-espree has exactly one reverse dependency which is >>> node-eslint-scope, so this is a case of bad coordination. >>> >>> (yes, another fix would be to upgrade node-eslint-scope, but that is >>> more complex and less urgent, so let's roll back first and work on >>> going forward in experimental first >> >> >> >> Node-espree was upgraded due to not compatible with acorn6... >> >> So upgrade is safer > > Please define "safer" in this context. > > - Jonas
Hi, <Disclamer: just to help - ignore if it doesn't - don't blame> * node-espree is a test dependency of node-eslint-scope in unstable * node-espree is a dependency of eslint (new package in experimental) * last eslint (6.8.0) depends on espree ≥ 6 * eslint experimental version is 4.18.2 * last eslint depends on babel 7 * node-espree <6 is broken by acorn 6 * acorn update is part of the difficult Node.js 12 upgrade (with rollup-1, gulp 4,...) I think we should prioritize Node.js upgrade here (needs a transition), then babel 7, then upgrade eslint to the last version </Disclamer>