I am attempting to package the latest upstream version of "trash-cli"¹,
which differs quite a lot from the current package on the build side of
The problem occurs during the post-build test phase. The tests cannot
find the scripts they are trying to test. The build appears to be a
standard python setuptools/distutils thing and the packaging is a
standard dh --with python3 --buildsystem=pybuild. The Build runs
/usr/bin/python3 setup.py build
Which outputs the following (elided)
copying trashcli/fstab.py ->
So for the build_py phase, the destination for copied files is rooted
under <>. The next build phase handles scripts:
copying and adjusting trash -> build/scripts-3.9
Here, the scripts are copied to a path *not* rooted in <>.
So far as I can tell, both phases are normal parts of the
setuptools/distutils build lifecycle, and I haven't spotted anything
obviously non-standard about the way that is specified.
Where is it that the build_py phase's path are specified or overridden
such that they are correctly rooted under <>, and why isn't
the same true of the build_scripts phase?
I've pushed my WIP packaging to a temporary branch.
A BTS bug requesting the new version with some back-and-forth trying to
figure this out is
Thank you in advance for any tips you can offer!