On Wed, 13 Feb 2019 22:18:18 +0100 Christian Kastner <c...@debian.org> wrote:
> Package: debhelper
> Version: 12.1
> Severity: normal
> 
> I just uploaded libmpikmeans_1.5+dfsg-6. During its build, I noticed
> dh_missing report two files, even though they were installed.
> 
> With an override and dh_missing --fail-tmp, I get
> 
>   dh_missing: usr/bin/mpi_assign exists in debian/tmp but is not installed to 
> anywhere
>   dh_missing: usr/bin/mpi_kmeans exists in debian/tmp but is not installed to 
> anywhere
>   dh_missing: missing files, aborting
> 
> but these binaries have always been listed in
> debian/mpikmeans-tools.install:
>   mpi_kmeans usr/bin
>   mpi_assign usr/bin
> 
> And they are installed correctly, eg `find debian -name mpi_kmeans`
> 
>   ./debian/tmp/usr/bin/mpi_kmeans
>   ./debian/mpikmeans-tools/usr/bin/mpi_kmeans
> 
> Regards,
> Christian
> 
> [...]
Hi Christian,

Thanks for taking the time to report this issue.

This occurs because the package is installing "mpi_kmeans" (from source
root) rather than "usr/bin/mpi_kmeans" (from debian/tmp).  In this
sense, dh_missing is "right" on a technicality that in practise is
irrelevant as the two different paths have the same content.

Honestly, I would recommend that you updated your install files to use
"usr/bin/mpi_kmeans" and "usr/bin/mpi_assign" as the solution.

Most likely, I will simply end up with a documentation note in
dh_missing about this case (wording suggestions/patches welcome).

Thanks,
~Niels

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to