Le dim. 21 juin 2026 à 16:15, Santiago Vila <[email protected]> a écrit :
> On Sun, Jun 21, 2026 at 03:46:50PM +0200, Jérémy Lal wrote: > > > at async ModuleJob.run (node:internal/modules/esm/module_job:431:5) > > > at async onImport.tracePromise.__proto__ > > > (node:internal/modules/esm/loader:633:26) > > > at async asyncRunEntryPointWithESMLoader > > > (node:internal/modules/run_main:96:9) > > > > > > Node.js v24.17.0 > > > make[2]: *** [Makefile:89: generate] Error 1 > > > make[2]: Leaving directory '/<<PKGBUILDDIR>>' > > > rm: cannot remove 'release/LICENSE': No such file or directory > > > rm: cannot remove 'release/README.md': No such file or directory > > > make[1]: *** [debian/rules:52: release] Error 1 > > > make[1]: Leaving directory '/<<PKGBUILDDIR>>' > > > make: *** [debian/rules:17: binary] Error 2 > > > dpkg-buildpackage: error: debian/rules binary subprocess failed with > exit > > > status 2 > > > > > > Any ideas? > > > > This one is fixed in node-tsx 4.22.4+~cs13.31.0-2 > > Ack. Sorry, I did not realize that the above error was from a build log > created yesterday. > > The error today is different: > > Install main build dependencies (apt-based resolver) > ---------------------------------------------------- > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > Solving dependencies... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > sbuild-build-depends-main-dummy : Depends: debhelper-compat (= 13) > Depends: dh-cmake-compat (= 1) > Depends: dh-cmake but it is not going > to be installed > Depends: cmake but it is not going to > be installed > Depends: libllhttp-source (>= > 9.4.2+~cs12.11.9~) but it is not going to be installed > Depends: dh-nodejs but it is not going > to be installed > Depends: binaryen but it is not going > to be installed > Depends: clang but it is not going to > be installed > Depends: libclang-rt-dev-wasm32 but it > is not going to be installed > Depends: lld (>= 1:16) but it is not > going to be installed > Depends: node-debug but it is not going > to be installed > Depends: node-markdown-it (>= > 22.2.3+dfsg+~12.2.3-2~) but it is not going to be installed > Depends: node-semver but it is not > going to be installed > Depends: node-typescript but it is not > going to be installed > Depends: node-tsx > Depends: ts-node but it is not going to > be installed > Depends: wasi-libc but it is not going > to be installed > E: Unable to satisfy dependencies. Reached two conflicting assignments: > 1. webpack:amd64=5.107.2+dfsg1+~cs15.16.25-1 is selected for install > because: > 1. sbuild-build-depends-main-dummy:amd64=0.invalid.0 is selected for > install > 2. sbuild-build-depends-main-dummy:amd64 Depends node-tsx > 3. tsx:amd64 Depends node-fastest-levenshtein > 2. webpack:amd64 Depends node-eslint-visitor-keys > but none of the choices are installable: > - node-eslint-visitor-keys:amd64 is available in version > 3.3.0+~1.0.0-2 > but none of the choices are installable: > - node-eslint-visitor-keys:amd64=3.3.0+~1.0.0-2 is not selected > for install because: > 1. sbuild-build-depends-main-dummy:amd64=0.invalid.0 is selected > for install as above > 2. sbuild-build-depends-main-dummy:amd64 Depends ts-node > 3. ts-node:amd64 Depends node-acorn > 4. node-acorn:amd64 Breaks node-eslint-visitor-keys (< > 3.3.0+~1.0.0-3~) > apt-get failed. > E: Package installation failed > > > I have no idea about what could be the reason for this. Yadd fixed the issue with node-tsx (that was my bad). Rouca is currently working on webpack, and he made some uploads today, hopefully fixing it.
-- Pkg-javascript-devel mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
