Your message dated Sun, 08 Mar 2026 18:01:34 +0000
with message-id <[email protected]>
and subject line Bug#1126218: fixed in node-import-meta-resolve 4.2.0-1
has caused the Debian Bug report #1126218,
regarding node-import-meta-resolve: FTBFS: lib/resolve.js(69,3): error TS2578:
Unused '@ts-expect-error' directive.
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1126218: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1126218
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:node-import-meta-resolve
Version: 4.1.0-1
Severity: serious
Tags: ftbfs forky sid
Dear maintainer:
During a rebuild of all packages in unstable, this package failed to build.
Below you will find the last part of the build log (probably the most
relevant part, but not necessarily). If required, the full build log
is available here:
https://people.debian.org/~sanvila/build-logs/202601/
About the archive rebuild: The build was made on virtual machines from AWS,
using sbuild and a reduced chroot with only build-essential packages.
If you cannot reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.
If this is really a bug in one of the build-depends, please use
reassign and add an affects on src:node-import-meta-resolve, so that this is
still
visible in the BTS web page for this package.
Thanks.
--------------------------------------------------------------------------------
[...]
debian/rules clean
dh clean
dh_auto_clean --buildsystem=nodejs
rm -rf ./node_modules/.cache ./.nyc_output
rm ./node_modules/.cache
unlink ./node_modules/@types/node
Trying to remove ./node_modules/@types
unlink ./node_modules/semver
rm ./node_modules/.cache
unlink ./node_modules/@types/node
Trying to remove ./node_modules/@types
unlink ./node_modules/semver
dh_clean
debian/rules execute_after_dh_clean
make[1]: Entering directory '/<<PKGBUILDDIR>>'
rm -f test/baseline*.js
rm -f test/node_modules/import-meta-resolve
rm -f *.d.ts lib/*.d.ts
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
debian/rules binary
dh binary
dh_update_autotools_config
dh_autoreconf
dh_auto_configure --buildsystem=nodejs
Link ./node_modules/@types/node -> /usr/share/nodejs/@types/node
Link ./node_modules/semver -> /usr/share/nodejs/semver
dh_auto_build --buildsystem=nodejs
Found debian/nodejs/./build
cd ./. && sh -ex debian/nodejs/./build
+ tsc --build
lib/resolve.js(69,3): error TS2578: Unused '@ts-expect-error' directive.
lib/resolve.js(100,3): error TS2578: Unused '@ts-expect-error' directive.
lib/resolve.js(677,3): error TS2578: Unused '@ts-expect-error' directive.
dh_auto_build: error: cd ./. && sh -ex debian/nodejs/./build returned exit code
1
make: *** [debian/rules:8: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess failed with exit
status 2
--------------------------------------------------------------------------------
--- End Message ---
--- Begin Message ---
Source: node-import-meta-resolve
Source-Version: 4.2.0-1
Done: Xavier Guimard <[email protected]>
We believe that the bug you reported is fixed in the latest version of
node-import-meta-resolve, which is due to be installed in the Debian FTP
archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Xavier Guimard <[email protected]> (supplier of updated node-import-meta-resolve
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Sun, 08 Mar 2026 17:47:29 +0100
Source: node-import-meta-resolve
Architecture: source
Version: 4.2.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers
<[email protected]>
Changed-By: Xavier Guimard <[email protected]>
Closes: 1126218
Changes:
node-import-meta-resolve (4.2.0-1) unstable; urgency=medium
.
* Team upload
* Declare compliance with policy 4.7.3
* Drop "Rules-Requires-Root: no"
* debian/watch version 5
* New upstream version 4.2.0
* Drop test_no_extra_deps.patch, now included in upstream
* Add debian/clean
* Update test
* Update typescript patch:
- dont follow symlinks
- replace @ts-expect-error with @ts-ignore (Closes: #1126218)
- fix JSDoc template use for tsc 5.0 (upstream uses 5.9)
Checksums-Sha1:
fd6a3c408f695f4f66d1c84f660ddb810927e42c 2247
node-import-meta-resolve_4.2.0-1.dsc
7b9392b1985ee403ae68bc616acab0e293f2690c 24960
node-import-meta-resolve_4.2.0.orig.tar.gz
f4eb3bc62c47fa10f858b00eb1a5194e4b6d6530 4428
node-import-meta-resolve_4.2.0-1.debian.tar.xz
Checksums-Sha256:
0548e62520b05eec71fa63f16be5c725a38f972dbb5b4bb432fc5a721f4a3e8a 2247
node-import-meta-resolve_4.2.0-1.dsc
defef5860ca537c24562515ec0bfc38ff8840ea3e4b12778d27fa018b97321cb 24960
node-import-meta-resolve_4.2.0.orig.tar.gz
0a2a9a848f65dd6ad55f855954c25bd7dbf8cca930158f6dd1562b1a8b28814e 4428
node-import-meta-resolve_4.2.0-1.debian.tar.xz
Files:
689c21fb5738c9068fc1d60a4a313aae 2247 javascript optional
node-import-meta-resolve_4.2.0-1.dsc
f2dc10e8d307b650e8c9fd82293c892d 24960 javascript optional
node-import-meta-resolve_4.2.0.orig.tar.gz
31d9080288be314055b4532e24a48bc4 4428 javascript optional
node-import-meta-resolve_4.2.0-1.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmmtqIwACgkQ9tdMp8mZ
7unZtQ/+JfGycYHm3U8XmFA5Sf+BrP/rDXYtm6a1fy0wif220joqfm8y2PPZ0QDP
8loe7HklyxdewRPZeiv0b74HobvHKSPxcVE+qKwT60Hx0EU5uh3lAPzGud07/rTV
iuL8yiTwRDJ3dou6HzwwBDAyj9/gArvgtYsYmzxDrJyt2QWvFpMV3DcBXAim8Ouh
nvjrSpd+CseAUJsQTYkMoxUI8xAKRtd8kLsQZISTzNFirT1ihCQjxRw3aKE3LowT
hCbIM95kcrh0BkUhQbDgzUlrd3g9Jvbv4F3oVKxGgJU/jLkMyxwjo9PsTgci8l5/
SEEArWFxqVCjLFaBNzGf5qATQDLjWtCN9jqKiN79U+0MZHUkRSe+gtEqlhhO6bHq
Ej7ibpRmxdStuZKarFZeN6Gidi8dHiXEPG6DpIOvzSdx+zaUUz5VvC/kHoOQP51f
nR8KtwJqUhW3/YiFruYQfkfJUvWCVCPPuMcBRBdTergIqc/1Ab24q5buFsDQnbgC
6lR9kTVanRRe5Bh1m4JiGxydZkcihJPBxnB8iMJCjwI24V9L230wbP6Wy+KmUvbr
HSwd+jwZuJr3gCi6cQLc9xOxpj5I5fIPQP3Jda4x7SgfK0Rb1MlSwykwBd9JZieP
oHVE6WolEmAjq4eM1dUMb34rzMpo1WleiGIsXGxZxDFzX8rf0Mc=
=Bjj/
-----END PGP SIGNATURE-----
pgpAfo7lZDtgQ.pgp
Description: PGP signature
--- End Message ---
