[Pkg-javascript-devel] RFH: FTBFS problem with jekyll build because some node* packages were updated

[Xavier]

Le 25/10/2020 à 21:04, Xavier a écrit :
> Le 25/10/2020 à 20:42, Pirate Praveen a écrit :
>> [Adding pkg-javascript-devel list]
>>
>> On 2020, ഒക്‌ടോബർ 26 12:14:08 AM IST, Daniel Leidert <dleidert at debian.org> wrote:
>>> Hi,
>>>
>>> the jekyll build fails at the moment because livereload.js created in the
>>> override_dh_auto_build target is not created. The creation prints some
>>> warnings:
>>>
>>>> make[1]: Entering directory '/tmp/build-area/jekyll-3.9.0+dfsg'
>>>> cd debian/node_modules/livereload-js; webpack --entry ./lib/startup.js \
>>>> --output ../../../lib/jekyll/commands/serve/livereload_assets/livereload.js; cd -
>>>> (node:391702) UnhandledPromiseRejectionWarning: TypeError: invalid options argument
>>>>     at optsArg (/usr/share/nodejs/mkdirp/lib/opts-arg.js:13:11)
>>>>     at NodeOutputFileSystem.mkdirp (/usr/share/nodejs/mkdirp/index.js:11:10)
>>>>     at /usr/share/nodejs/webpack/lib/Compiler.js:494:26
>>>>     at AsyncSeriesHook.eval [as callAsync] (eval at create (/usr/share/nodejs/tapable/lib/HookCodeFactory.js:24:12), <anonymous>:4:1)
>>>>     at AsyncSeriesHook.lazyCompileHook [as _callAsync] (/usr/share/nodejs/tapable/lib/Hook.js:35:21)
>>>>     at Compiler.emitAssets (/usr/share/nodejs/webpack/lib/Compiler.js:491:19)
>>>>     at onCompiled (/usr/share/nodejs/webpack/lib/Compiler.js:278:9)
>>>>     at /usr/share/nodejs/webpack/lib/Compiler.js:681:15
>>>>     at AsyncSeriesHook.eval [as callAsync] (eval at create (/usr/share/nodejs/tapable/lib/HookCodeFactory.js:24:12), <anonymous>:4:1)
>>>>     at AsyncSeriesHook.lazyCompileHook [as _callAsync] (/usr/share/nodejs/tapable/lib/Hook.js:35:21)
>>>>     at /usr/share/nodejs/webpack/lib/Compiler.js:678:31
>>>>     at AsyncSeriesHook.eval [as callAsync] (eval at create (/usr/share/nodejs/tapable/lib/HookCodeFactory.js:24:12), <anonymous>:4:1)
>>>>     at AsyncSeriesHook.lazyCompileHook [as _callAsync] (/usr/share/nodejs/tapable/lib/Hook.js:35:21)
>>>>     at /usr/share/nodejs/webpack/lib/Compilation.js:1423:35
>>>>     at AsyncSeriesHook.eval [as callAsync] (eval at create (/usr/share/nodejs/tapable/lib/HookCodeFactory.js:24:12), <anonymous>:4:1)
>>>>     at AsyncSeriesHook.lazyCompileHook [as _callAsync] (/usr/share/nodejs/tapable/lib/Hook.js:35:21)
>>>>     at /usr/share/nodejs/webpack/lib/Compilation.js:1414:32
>>>>     at eval (eval at create (/usr/share/nodejs/tapable/lib/HookCodeFactory.js:24:12), <anonymous>:9:1)
>>>>     at /usr/share/nodejs/uglifyjs-webpack-plugin/dist/index.js:263:11
>>>>     at step (/usr/share/nodejs/uglifyjs-webpack-plugin/dist/uglify/Runner.js:98:11)
>>>>     at done (/usr/share/nodejs/uglifyjs-webpack-plugin/dist/uglify/Runner.js:110:22)
>>>> (node:391702) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
>>>> (node:391702) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
>>>> /tmp/build-area/jekyll-3.9.0+dfsg
>>>
>>> I was able to restore the old behavior in Sid via:
>>>
>>> sudo apt-get install node-cacache=11.3.3-2 node-mkdirp=0.5.1-2 \
>>>                     node-copy-concurrently=1.0.5-5 webpack+
>>>
>>> But I really need help fixing whatever the problem is with the updated node*
>>> packages. Any help is appreciated.
>>
>> This is the result of node-mkdirp transition.
>>
>> See https://alioth-lists.debian.net/pipermail/pkg-javascript-devel/2020-October/045643.html
>>
>>> Regards, Daniel
> 
> Sadly debci didn't show this problem before transition, I' going to fix
> webpack

Fixed in 4.43.0-2, sorry for this. Now your build fails but for other
reasons...

Cheers,
Xavier