[Pkg-javascript-devel] Bug#1048645: node-propagate: Fails to build source after successful build

[Lucas Nussbaum]

Source: node-propagate
Version: 2.0.1-4
Severity: minor
Tags: trixie sid ftbfs
User: lucas at debian.org
Usertags: ftbfs-sab-20230813 ftbfs-source-after-build
User: debian-qa at lists.debian.org
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-propagate
> dpkg-buildpackage: info: source version 2.0.1-4
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Yadd <yadd at debian.org>
>  dpkg-source --before-build .
>  debian/rules clean
> dh clean
>    debian/rules override_dh_auto_clean
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> dh_auto_clean
> test -e package.json.save && mv package.json.save package.json
> make[1]: Leaving directory '/<<PKGBUILDDIR>>'
>    dh_clean
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building node-propagate using existing ./node-propagate_2.0.1.orig.tar.gz
> dpkg-source: warning: file node-propagate-2.0.1/.nyc_output/4fdc6eb4-2384-4673-bda2-0e1841365490.json has no final newline (either original or modified version)
> dpkg-source: warning: file node-propagate-2.0.1/.nyc_output/d9152685-bb03-4987-98e9-5df54ed8d65e.json has no final newline (either original or modified version)
> dpkg-source: warning: file node-propagate-2.0.1/.nyc_output/processinfo/4fdc6eb4-2384-4673-bda2-0e1841365490.json has no final newline (either original or modified version)
> dpkg-source: warning: file node-propagate-2.0.1/.nyc_output/processinfo/d9152685-bb03-4987-98e9-5df54ed8d65e.json has no final newline (either original or modified version)
> dpkg-source: warning: file node-propagate-2.0.1/.nyc_output/processinfo/index.json has no final newline (either original or modified version)
> dpkg-source: warning: file node-propagate-2.0.1/node_modules/.cache/nyc/index-13e29f827013451738e5ea6cf3968e1406536cb8f4490e5bb3f78b925328acb6.js has no final newline (either original or modified version)
> dpkg-source: info: local changes detected, the modified files are:
>  node-propagate-2.0.1/.nyc_output/4fdc6eb4-2384-4673-bda2-0e1841365490.json
>  node-propagate-2.0.1/.nyc_output/d9152685-bb03-4987-98e9-5df54ed8d65e.json
>  node-propagate-2.0.1/.nyc_output/processinfo/4fdc6eb4-2384-4673-bda2-0e1841365490.json
>  node-propagate-2.0.1/.nyc_output/processinfo/d9152685-bb03-4987-98e9-5df54ed8d65e.json
>  node-propagate-2.0.1/.nyc_output/processinfo/index.json
>  node-propagate-2.0.1/node_modules/.cache/nyc/index-13e29f827013451738e5ea6cf3968e1406536cb8f4490e5bb3f78b925328acb6.js
> dpkg-source: error: aborting due to unexpected upstream changes, see /tmp/node-propagate_2.0.1-4.diff.vNMEm7
> 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-propagate_2.0.1-4_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.