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

[Lucas Nussbaum]

Source: node-bluebird
Version: 3.7.2+dfsg1+~3.5.36-1
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-bluebird
> dpkg-buildpackage: info: source version 3.7.2+dfsg1+~3.5.36-1
> 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
>    dh_auto_clean --buildsystem=nodejs
> 	rm -rf ./node_modules/.cache ./.nyc_output
> 	rm -rf types-bluebird/node_modules/.cache types-bluebird/.nyc_output
> rm ./node_modules/.cache
> unlink ./node_modules/bluebird
> rm types-bluebird/node_modules/.cache
> unlink node_modules/@types/bluebird
>    dh_clean
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building node-bluebird using existing ./node-bluebird_3.7.2+dfsg1+~3.5.36.orig-types-bluebird.tar.xz
> dpkg-source: info: building node-bluebird using existing ./node-bluebird_3.7.2+dfsg1+~3.5.36.orig.tar.xz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: warning: ignoring deletion of directory js
> dpkg-source: info: local changes detected, the modified files are:
>  node-bluebird-3.7.2+dfsg1+~3.5.36/node_modules/bluebird/js/release/any.js
>  node-bluebird-3.7.2+dfsg1+~3.5.36/node_modules/bluebird/js/release/assert.js
>  node-bluebird-3.7.2+dfsg1+~3.5.36/node_modules/bluebird/js/release/async.js
>  node-bluebird-3.7.2+dfsg1+~3.5.36/node_modules/bluebird/js/release/bind.js
>  node-bluebird-3.7.2+dfsg1+~3.5.36/node_modules/bluebird/js/release/bluebird.js
>  node-bluebird-3.7.2+dfsg1+~3.5.36/node_modules/bluebird/js/release/call_get.js
>  node-bluebird-3.7.2+dfsg1+~3.5.36/node_modules/bluebird/js/release/cancel.js
>  node-bluebird-3.7.2+dfsg1+~3.5.36/node_modules/bluebird/js/release/catch_filter.js
>  node-bluebird-3.7.2+dfsg1+~3.5.36/node_modules/bluebird/js/release/context.js
>  node-bluebird-3.7.2+dfsg1+~3.5.36/node_modules/bluebird/js/release/debuggability.js
>  node-bluebird-3.7.2+dfsg1+~3.5.36/node_modules/bluebird/js/release/direct_resolve.js
>  node-bluebird-3.7.2+dfsg1+~3.5.36/node_modules/bluebird/js/release/each.js
>  node-bluebird-3.7.2+dfsg1+~3.5.36/node_modules/bluebird/js/release/errors.js
>  node-bluebird-3.7.2+dfsg1+~3.5.36/node_modules/bluebird/js/release/es5.js
>  node-bluebird-3.7.2+dfsg1+~3.5.36/node_modules/bluebird/js/release/filter.js
>  node-bluebird-3.7.2+dfsg1+~3.5.36/node_modules/bluebird/js/release/finally.js
>  node-bluebird-3.7.2+dfsg1+~3.5.36/node_modules/bluebird/js/release/generators.js
>  node-bluebird-3.7.2+dfsg1+~3.5.36/node_modules/bluebird/js/release/join.js
>  node-bluebird-3.7.2+dfsg1+~3.5.36/node_modules/bluebird/js/release/map.js
>  node-bluebird-3.7.2+dfsg1+~3.5.36/node_modules/bluebird/js/release/method.js
>  node-bluebird-3.7.2+dfsg1+~3.5.36/node_modules/bluebird/js/release/nodeback.js
>  node-bluebird-3.7.2+dfsg1+~3.5.36/node_modules/bluebird/js/release/nodeify.js
>  node-bluebird-3.7.2+dfsg1+~3.5.36/node_modules/bluebird/js/release/promise.js
>  node-bluebird-3.7.2+dfsg1+~3.5.36/node_modules/bluebird/js/release/promise_array.js
>  node-bluebird-3.7.2+dfsg1+~3.5.36/node_modules/bluebird/js/release/promisify.js
>  node-bluebird-3.7.2+dfsg1+~3.5.36/node_modules/bluebird/js/release/props.js
>  node-bluebird-3.7.2+dfsg1+~3.5.36/node_modules/bluebird/js/release/queue.js
>  node-bluebird-3.7.2+dfsg1+~3.5.36/node_modules/bluebird/js/release/race.js
>  node-bluebird-3.7.2+dfsg1+~3.5.36/node_modules/bluebird/js/release/reduce.js
>  node-bluebird-3.7.2+dfsg1+~3.5.36/node_modules/bluebird/js/release/schedule.js
>  node-bluebird-3.7.2+dfsg1+~3.5.36/node_modules/bluebird/js/release/settle.js
>  node-bluebird-3.7.2+dfsg1+~3.5.36/node_modules/bluebird/js/release/some.js
>  node-bluebird-3.7.2+dfsg1+~3.5.36/node_modules/bluebird/js/release/synchronous_inspection.js
>  node-bluebird-3.7.2+dfsg1+~3.5.36/node_modules/bluebird/js/release/thenables.js
>  node-bluebird-3.7.2+dfsg1+~3.5.36/node_modules/bluebird/js/release/timers.js
>  node-bluebird-3.7.2+dfsg1+~3.5.36/node_modules/bluebird/js/release/using.js
>  node-bluebird-3.7.2+dfsg1+~3.5.36/node_modules/bluebird/js/release/util.js
>  node-bluebird-3.7.2+dfsg1+~3.5.36/node_modules/bluebird/package.json
> dpkg-source: error: aborting due to unexpected upstream changes, see /tmp/node-bluebird_3.7.2+dfsg1+~3.5.36-1.diff.hkgiMW
> 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-bluebird_3.7.2+dfsg1+~3.5.36-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.