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

Lucas Nussbaum lucas at debian.org
Sun Aug 13 20:21:02 BST 2023


Source: node-mocha
Version: 10.1.0+ds1+~cs29.3.1-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-mocha
> dpkg-buildpackage: info: source version 10.1.0+ds1+~cs29.3.1-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 flat/node_modules/.cache flat/.nyc_output
> 	rm -rf log-symbols/node_modules/.cache log-symbols/.nyc_output
> 	rm -rf types-mocha/node_modules/.cache types-mocha/.nyc_output
> 	rm -rf workerpool/node_modules/.cache workerpool/.nyc_output
> 	rm -rf yargs-unparser/node_modules/.cache yargs-unparser/.nyc_output
> rm ./node_modules/.cache
> rm flat/node_modules/.cache
> rm log-symbols/node_modules/.cache
> rm types-mocha/node_modules/.cache
> rm workerpool/node_modules/.cache
> rm yargs-unparser/node_modules/.cache
> unlink node_modules/flat
> unlink node_modules/log-symbols
> unlink node_modules/@types/mocha
> unlink node_modules/workerpool
> unlink node_modules/yargs-unparser
>    dh_clean
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building node-mocha using existing ./node-mocha_10.1.0+ds1+~cs29.3.1.orig-flat.tar.xz
> dpkg-source: info: building node-mocha using existing ./node-mocha_10.1.0+ds1+~cs29.3.1.orig-log-symbols.tar.xz
> dpkg-source: info: building node-mocha using existing ./node-mocha_10.1.0+ds1+~cs29.3.1.orig-types-mocha.tar.xz
> dpkg-source: info: building node-mocha using existing ./node-mocha_10.1.0+ds1+~cs29.3.1.orig-workerpool.tar.xz
> dpkg-source: info: building node-mocha using existing ./node-mocha_10.1.0+ds1+~cs29.3.1.orig-yargs-unparser.tar.xz
> dpkg-source: info: building node-mocha using existing ./node-mocha_10.1.0+ds1+~cs29.3.1.orig.tar.xz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: info: local changes detected, the modified files are:
>  node-mocha-10.1.0+ds1+~cs29.3.1/flat/package.json
> dpkg-source: error: aborting due to unexpected upstream changes, see /tmp/node-mocha_10.1.0+ds1+~cs29.3.1-1.diff.WFchQ6
> 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-mocha_10.1.0+ds1+~cs29.3.1-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.



More information about the Pkg-javascript-devel mailing list