On 18/03/2022 13:23, Jérémy Lal wrote:


On Fri, Mar 18, 2022 at 1:21 PM Yadd <y...@debian.org <mailto:y...@debian.org>> wrote:

    On 18/03/2022 09:38, Jérémy Lal wrote:
     > Package: node-inquirer
     > Version: 8.2.0+~cs26.5.5-1
     > Severity: serious
     > Tags: ftbfs
     > Justification: fails to build from source
     >
     > Found debian/nodejs/additional_components
     > Adding component(s): packages/checkbox, packages/confirm,
    packages/core, packages/editor, packages/expand, packages/input,
    packages/inquirer, packages/password, packages/select
     > No build command found, searching known files
     > Found debian/nodejs/figures/build
     >       cd ./figures && sh -ex ../debian/nodejs/figures/build
     > + babeljs --presets @babel/preset-env -o index.cjs index.js
     > No build command found, searching known files
     > Found debian/nodejs/rxjs/build
     >       cd ./rxjs && sh -ex ../debian/nodejs/rxjs/build
     > + rm -rf ./dist
     > + tsc -b ./src/tsconfig.cjs.json ./src/tsconfig.esm.json
    ./src/tsconfig.esm5.json ./src/tsconfig.esm5.rollup.json
    ./src/tsconfig.types.json ./spec/tsconfig.json
     > + find dist/ -type f -name *.tsbuildinfo -delete
     > + node ./tools/make-umd-bundle.js
     > TypeError [ERR_INVALID_ARG_TYPE]: The "data" argument must be of
    type string or an instance of Buffer, TypedArray, or DataView.
    Received undefined
     >      at Object.writeFileSync (fs.js:1521:5)
     >      at
    
/var/lib/nspawn-runner/.build/js-team/nodejs/debian/output/node-inquirer-8.2.0+~cs26.5.5/rxjs/tools/rollup-bundle.js:45:8
     >      at runMicrotasks (<anonymous>)
     >      at processTicksAndRejections
    (internal/process/task_queues.js:95:5) {
     >    code: 'ERR_INVALID_ARG_TYPE'
     > }
     > dh_auto_build: error: cd ./rxjs && sh -ex
    ../debian/nodejs/rxjs/build returned exit code 1
     > make: *** [debian/rules:8: binary] Error 25
     > dpkg-buildpackage: error: debian/rules binary subprocess returned
    exit status 2

    The various tsc problems ca come:
       * from a previous undetected @types/foo change
       * from @types/node update
       * from new node_modules links which may show problems ignored before

    Here, problem isn't linked to tsc but maybe due to fs API changes. I'm
    going to take a look.


That makes sense to me.
I can have a look later today if you don't want to lose time on this.

Jérémy

Problem is in rollup job. Sourcemap data is undefined, that why this error is reported

Reply via email to