Source: node-mdn-browser-compat-data
Version: 5.2.20+~3.33.0-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> ts-node scripts/generate-types.ts
> TypeError [ERR_UNKNOWN_FILE_EXTENSION]: Unknown file extension ".ts" for
> /<<PKGBUILDDIR>>/scripts/generate-types.ts
> at new NodeError (node:internal/errors:405:5)
> at Object.getFileProtocolModuleFormat [as file:]
> (node:internal/modules/esm/get_format:136:11)
> at defaultGetFormat (node:internal/modules/esm/get_format:182:36)
> at defaultLoad (node:internal/modules/esm/load:101:20)
> at nextLoad (node:internal/modules/esm/hooks:864:28)
> at load (/usr/share/nodejs/ts-node/dist/child/child-loader.js:19:122)
> at nextLoad (node:internal/modules/esm/hooks:864:28)
> at Hooks.load (node:internal/modules/esm/hooks:447:26)
> at MessagePort.handleMessage (node:internal/modules/esm/worker:196:24)
> at [nodejs.internal.kHybridDispatch] (node:internal/event_target:786:20) {
> code: 'ERR_UNKNOWN_FILE_EXTENSION'
> }
> make[1]: *** [debian/rules:11: override_dh_auto_build] Error 1
The full build log is available from:
http://qa-logs.debian.net/2023/12/12/node-mdn-browser-compat-data_5.2.20+~3.33.0-1_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20231212&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
