[Pkg-javascript-devel] Bug#1057934: libjs-jquery-jstree: FTBFS: dh_debputy: error: debputy internal-command dh-integration-generate-debs -p libjs-jquery-jstree .. returned exit code 1

[Santiago Vila]

Package: src:libjs-jquery-jstree
Version: 3.3.16+dfsg1-1
Severity: serious
Tags: ftbfs

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:

--------------------------------------------------------------------------------
[...]
  debian/rules binary
dh binary
    dh_update_autotools_config
    dh_autoreconf
    debian/rules override_dh_auto_build
make[1]: Entering directory '/<<PKGBUILDDIR>>'
cp debian/build.js build.js
nodejs /usr/share/nodejs/requirejs/r.js -o build.js

Tracing dependencies for: jstree

/<<PKGBUILDDIR>>/dist/jstree.js
----------------
/<<PKGBUILDDIR>>/src/jstree.js
/<<PKGBUILDDIR>>/src/jstree.changed.js
/<<PKGBUILDDIR>>/src/jstree.checkbox.js
/<<PKGBUILDDIR>>/src/jstree.conditionalselect.js
/<<PKGBUILDDIR>>/src/jstree.contextmenu.js
/<<PKGBUILDDIR>>/src/jstree.dnd.js
/<<PKGBUILDDIR>>/src/jstree.massload.js
/<<PKGBUILDDIR>>/src/jstree.search.js
/<<PKGBUILDDIR>>/src/jstree.sort.js
/<<PKGBUILDDIR>>/src/jstree.state.js
/<<PKGBUILDDIR>>/src/jstree.types.js
/<<PKGBUILDDIR>>/src/jstree.unique.js
/<<PKGBUILDDIR>>/src/jstree.wholerow.js
/<<PKGBUILDDIR>>/src/vakata-jstree.js

sed -i -e 's/{{VERSION}}/3.3.16+dfsg1/' dist/jstree.js
Checking syntax of dist/jstree.js ...
uglifyjs dist/jstree.js --output dist/jstree.min.js --compress
dh_auto_build
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
    debian/rules override_dh_auto_test
make[1]: Entering directory '/<<PKGBUILDDIR>>'
nodejs --check dist/jstree.js
nodejs --check dist/jstree.min.js
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
    create-stamp debian/debhelper-build-stamp
    dh_prep
    dh_auto_install --destdir=debian/libjs-jquery-jstree/
    dh_debputy
Internal error in debputy
   ----- 8< ---- BEGIN STACK TRACE ---- 8< -----
Traceback (most recent call last):
   File "/usr/share/dh-debputy/debputy/commands/debputy_cmd.py", line 2082, in main
     command.handler(cmd_context)
   File "/usr/share/dh-debputy/debputy/commands/debputy_cmd.py", line 1133, in _dh_integration_generate_debs
     intermediate_manifest = manifest.finalize_data_tar_contents(
                             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   File "/usr/share/dh-debputy/debputy/highlevel_manifest.py", line 1177, in finalize_data_tar_contents
     intermediate_manifest = list(
                             ^^^^^
   File "/usr/share/dh-debputy/debputy/highlevel_manifest.py", line 180, in _generate_intermediate_manifest
     tar_member = _path_to_tar_member(path, clamp_mtime_to)
                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   File "/usr/share/dh-debputy/debputy/highlevel_manifest.py", line 159, in _path_to_tar_member
     return TarMember.from_file(
            ^^^^^^^^^^^^^^^^^^^^
   File "/usr/share/dh-debputy/debputy/intermediate_manifest.py", line 147, in from_file
     "debputy/scratch_dir/" in fs_path
AssertionError: README.md should not have been stealable
   ----- 8< ---- END STACK TRACE ---- 8< -----
Please file a bug against debputy with the full output.
README.md should not have been stealable
dh_debputy: error: debputy internal-command dh-integration-generate-debs -p libjs-jquery-jstree .. returned exit code 1
make: *** [debian/rules:34: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
--------------------------------------------------------------------------------

The above is just how the build ends and not necessarily the most relevant part.
If required, the full build log is available here:

https://people.debian.org/~sanvila/build-logs/202312/

About the archive rebuild: The build was made using virtual machines
from AWS, with enough memory, enough disk, and either one or two
CPUs, using a reduced chroot with only build-essential packages.

If you could not reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.

If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the BTS web
page for this package.

Thanks.