Your message dated Mon, 09 Mar 2026 08:49:44 +0000
with message-id <[email protected]>
and subject line Bug#1048048: fixed in node-xterm 5.3.0-5
has caused the Debian Bug report #1048048,
regarding node-xterm: Fails to build source after successful build
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.)
--
1048048: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1048048
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: node-xterm
Version: 3.8.1+~cs0.9.0-1
Severity: minor
Tags: trixie sid ftbfs
User: [email protected]
Usertags: ftbfs-sab-20230813 ftbfs-source-after-build
User: [email protected]
Usertags: qa-doublebuild
Hi,
This package fails to build a source package after a successful build
(dpkg-buildpackage ; dpkg-buildpackage -S).
This is probably a clear violation of Debian Policy section 4.9 (clean target),
but this is filed as severity:minor for now, because a discussion on
debian-devel showed that we might want to revisit the requirement of a working
'clean' target.
More information about this class of issues, included common problems and
solutions, is available at
https://wiki.debian.org/qa.debian.org/FTBFS/SourceAfterBuild
Relevant part of the build log:
> cd /<<PKGBUILDDIR>> && runuser -u user42 -- dpkg-buildpackage --sanitize-env
> -us -uc -rfakeroot -S
> ------------------------------------------------------------------------------------------------------------------------------------
>
> dpkg-buildpackage: info: source package node-xterm
> dpkg-buildpackage: info: source version 3.8.1+~cs0.9.0-1
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Pirate Praveen <[email protected]>
> dpkg-source --before-build .
> debian/rules clean
> dh clean --with nodejs
> debian/rules override_dh_auto_clean
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> dh_auto_clean
> rm -rf node_modules lib dist build
> make[1]: Leaving directory '/<<PKGBUILDDIR>>'
> dh_clean
> dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building node-xterm using existing
> ./node-xterm_3.8.1+~cs0.9.0.orig-node-pty.tar.gz
> dpkg-source: info: building node-xterm using existing
> ./node-xterm_3.8.1+~cs0.9.0.orig.tar.gz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: error: cannot represent change to
> node-pty/node_modules/@types/mocha:
> dpkg-source: error: new version is symlink to /usr/share/nodejs/@types/mocha
> dpkg-source: error: old version is nonexistent
> dpkg-source: error: cannot represent change to
> node-pty/node_modules/@types/node:
> dpkg-source: error: new version is symlink to /usr/share/nodejs/@types/node
> dpkg-source: error: old version is nonexistent
> dpkg-source: warning: ignoring deletion of file src/Terminal.integration.ts,
> use --include-removal to override
> dpkg-source: error: unrepresentable changes to source
> dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 255
>
> E: Command 'cd /<<PKGBUILDDIR>> && runuser -u user42 -- dpkg-buildpackage
> --sanitize-env -us -uc -rfakeroot -S' failed to run.
The full build log is available from:
http://qa-logs.debian.net/2023/08/13/node-xterm_3.8.1+~cs0.9.0-1_unstable.log
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.
--- End Message ---
--- Begin Message ---
Source: node-xterm
Source-Version: 5.3.0-5
Done: Xavier Guimard <[email protected]>
We believe that the bug you reported is fixed in the latest version of
node-xterm, 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-xterm 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: Mon, 09 Mar 2026 08:43:28 +0100
Source: node-xterm
Architecture: source
Version: 5.3.0-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers
<[email protected]>
Changed-By: Xavier Guimard <[email protected]>
Closes: 1048048 1049844 1122450
Changes:
node-xterm (5.3.0-5) unstable; urgency=medium
.
[ Bastien Roucariès ]
* Team upload
* Depends on glob >= 10 (Closes: #1122450)
* Clean node_modules (Closes: #1048048, #1049844)
.
[ Xavier Guimard ]
* Fix build with nodejs 22
Checksums-Sha1:
62cad668653b628bf29740768ee8af067d2a011c 2541 node-xterm_5.3.0-5.dsc
ebd02bc80f086906708d9bf25ad006406308a52a 18240 node-xterm_5.3.0-5.debian.tar.xz
Checksums-Sha256:
7dc1f1a315cb62dd6376bd43fd2cc76e11d67cc5eb5983a2e1f9c78977a78888 2541
node-xterm_5.3.0-5.dsc
8fc73001a2146cd227a29b747f7e94c0ef4dcc7a1f9a03794b8345329d5ba610 18240
node-xterm_5.3.0-5.debian.tar.xz
Files:
98f336d243575bf09230da3f5f708906 2541 javascript optional
node-xterm_5.3.0-5.dsc
df75524bf28db0edf21ee7e744d18a10 18240 javascript optional
node-xterm_5.3.0-5.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmmuf3cACgkQ9tdMp8mZ
7ulxFw//bMVP+pEZI0xTdLpDRBtpOY5erSPNJv/0x4yt6F121cgLNoTcmQ2sYcqB
UDqhH54pTS7kkWCU0NV3B9L5W9qA8QjrBV1EyiDj/LAWANqXp7p2yfXLQWWJ1oU1
NlZ6Zam2mHU2ojE0nLzPZ+Or/AEsB7sr0OV0SwOxGmlBcsTy9nyP5tdTF1fnglIu
fIYdYgxB3ioC/iIJ4VPu4V8aluwqPDi9NEK0Vl79eWIgXtxQEugX7UWBA3sQrgwq
JZ7xks6mVoIBwqxCKOQyFlrwh75KRgulKV0D+HCKt3Yf+/PV3IeqNqUFM/ucKXnq
s3yeFT8F6VodFS0Mk4FpGuTqCb1QA8J55e0YunQ2EvkjGpF7Jqb+CtE5K9aqdWSZ
ztLhCeJp0+SNmyAH59eN1VIri4Ieb1zzTjC+JfRmkPYbdE/kU31HUObi0uScz+v5
CRN4zEEnyo/W0FEmhVs9Z/aswnU/IEmxdc2SfSQzg6pcuLMOvnokRVibEKPjlZbk
pkuTn8CMJEJY3yssl4Omd13r3f6MFYsS6OKYDgglN4HRFaZqAxZQ4yni1tSOLooK
E+J/w3e6gKgUu+NDdrPFsBjVdOrjumetXUX5IfPpEhM7LTLz6NYF5kqZQVSUCyxB
tXAlltx9ue1Fzdpkk5LfooagrC5ra6H8WQOOByIqSiT1xWI4Jpg=
=Z0aV
-----END PGP SIGNATURE-----
pgp9aNOgQsFye.pgp
Description: PGP signature
--- End Message ---
