Your message dated Fri, 20 Feb 2026 22:34:02 +0000
with message-id <[email protected]>
and subject line Bug#1046072: fixed in node-npm-run-path 5.1.0+~4.0.0-9
has caused the Debian Bug report #1046072,
regarding node-npm-run-path: 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.)


-- 
1046072: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1046072
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: node-npm-run-path
Version: 5.1.0+~4.0.0-8
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-npm-run-path
> dpkg-buildpackage: info: source version 5.1.0+~4.0.0-8
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Yadd <[email protected]>
>  dpkg-source --before-build .
>  debian/rules clean
> dh clean
>    dh_auto_clean --buildsystem=nodejs
>       rm -rf ./node_modules/.cache ./.nyc_output
>       rm -rf path-key/node_modules/.cache path-key/.nyc_output
> rm ./node_modules/.cache
> rm path-key/node_modules/.cache
> unlink node_modules/path-key
>    dh_clean
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building node-npm-run-path using existing 
> ./node-npm-run-path_5.1.0+~4.0.0.orig-path-key.tar.gz
> dpkg-source: info: building node-npm-run-path using existing 
> ./node-npm-run-path_5.1.0+~4.0.0.orig.tar.gz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: info: local changes detected, the modified files are:
>  node-npm-run-path-5.1.0+~4.0.0/package.json
>  node-npm-run-path-5.1.0+~4.0.0/path-key/package.json
> dpkg-source: error: aborting due to unexpected upstream changes, see 
> /tmp/node-npm-run-path_5.1.0+~4.0.0-8.diff.z6LLGn
> dpkg-source: info: Hint: make sure the version in debian/changelog matches 
> the unpacked source tree
> dpkg-source: info: you can integrate the local changes with dpkg-source 
> --commit
> dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2
> 
> 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-npm-run-path_5.1.0+~4.0.0-8_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-npm-run-path
Source-Version: 5.1.0+~4.0.0-9
Done: Santiago Vila <[email protected]>

We believe that the bug you reported is fixed in the latest version of
node-npm-run-path, 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.
Santiago Vila <[email protected]> (supplier of updated node-npm-run-path 
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: Fri, 20 Feb 2026 23:20:00 +0100
Source: node-npm-run-path
Architecture: source
Version: 5.1.0+~4.0.0-9
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 
<[email protected]>
Changed-By: Santiago Vila <[email protected]>
Closes: 1046072
Changes:
 node-npm-run-path (5.1.0+~4.0.0-9) unstable; urgency=medium
 .
   * Team upload.
   * Fix clean target. Closes: #1046072.
   * Drop "Rules-Requires-Root: no" (default).
   * Drop "Priority: optional" (default).
   * Update standards-version.
   * Simplify salsa-ci.yml.
Checksums-Sha1:
 62d5c85d19303bd2d880e88ae0bc8097ab990fb7 2148 
node-npm-run-path_5.1.0+~4.0.0-9.dsc
 0c29599446f6e531fda40c5dd90581e58528e1ea 5016 
node-npm-run-path_5.1.0+~4.0.0-9.debian.tar.xz
 75774e7ea7d83a0c25015e8444f136d198df66fb 8329 
node-npm-run-path_5.1.0+~4.0.0-9_source.buildinfo
Checksums-Sha256:
 dbc7b11d58eb306dfae5d217fbd2fe94ff19df445d49c8e7ae2870297b3f2494 2148 
node-npm-run-path_5.1.0+~4.0.0-9.dsc
 35eb275c4991b5d865b4ecb77aebadac1af2d7b6b98d0ab5c115944615bc35c4 5016 
node-npm-run-path_5.1.0+~4.0.0-9.debian.tar.xz
 c94ce839ce32ef7f6e15d9d328667e50201eeafa4ac0e4934716e1750f8cc5ab 8329 
node-npm-run-path_5.1.0+~4.0.0-9_source.buildinfo
Files:
 5b08acb9d9d75d6886c5a0f2db01185d 2148 javascript optional 
node-npm-run-path_5.1.0+~4.0.0-9.dsc
 ee32942e30128f7b66981d1cbc7af4bd 5016 javascript optional 
node-npm-run-path_5.1.0+~4.0.0-9.debian.tar.xz
 9a4df94bb456f6e02f387edeefb1cf24 8329 javascript optional 
node-npm-run-path_5.1.0+~4.0.0-9_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEE1Uw7+v+wQt44LaXXQc5/C58bizIFAmmY3tUACgkQQc5/C58b
izKceQf6A6rtYcmK6xaYToYHw4QrzOiu/fvKjH0ZSmV36QFDgGKxn93l8/ym3fJa
clgVka/hm+B7+YL9NfdX7UByFl6RwYaSwNceMGTbqZolsFQcVDU92Ntd5PQvat59
1cG+0ibf4dCVRSU5iQzKM+u/dhVrtZ9sfrdBgPEhIa2CZ9Y8YlsjLlJ3C48VaJgA
AmS04cavzHTZemQe79yCki3p9yGb7uDF55/nwUcoTQ2x7Co6qaOP7IqS1l1TcTbc
Ifms7pT6ygsbg48vlAg+ZeZHUV/x/b7T3Qcs8ftSwHSoxAd5RCYTIZfF+5BXa662
5jN2lE13MGCHdpOEasDQwf2/2dX07A==
=afbb
-----END PGP SIGNATURE-----

Attachment: pgpY0HgQS2Ye3.pgp
Description: PGP signature


--- End Message ---

Reply via email to