Source: jq
Version: 1.6-2
Severity: serious
Tags: ftbfs

jq fails to build from source on the buildds for any architecture. Here
is an example failure:

|    dh_missing -a
| dh_missing: warning: usr/lib/x86_64-linux-gnu/libjq.la exists in debian/tmp 
but is not installed to anywhere
| dh_missing: warning: usr/share/doc/jq/AUTHORS exists in debian/tmp but is not 
installed to anywhere (related file: "AUTHORS")
| dh_missing: warning: usr/share/doc/jq/README exists in debian/tmp but is not 
installed to anywhere (related file: "README")
| dh_missing: error: missing files, aborting
| 
|  While detecting missing files, dh_missing noted some files with a similar 
name to those
|  that were missing.  This error /might/ be resolved by replacing references 
to the
|  missing files with the similarly named ones that dh_missing found - assuming 
the content
|  is identical.
| 
|  As an example, you might want to replace:
|   * AUTHORS
|  with:
|   * usr/share/doc/jq/AUTHORS
|  in a file in debian/ or as argument to one of the dh_* tools called from 
debian/rules.
|  (Note it is possible the paths are not used verbatim but instead directories
|  containing or globs matching them are used instead)
| 
|  Alternatively, add the missing file to debian/not-installed if it cannot and 
should not
|  be used.
| 
|  The following debhelper tools have reported what they installed (with files 
per package)
|   * dh_install: jq (2), libjq-dev (3), libjq1 (2)
|   * dh_installdocs: jq (2), libjq-dev (0), libjq1 (0)
|   * dh_installman: jq (0), libjq-dev (0), libjq1 (0)
|  If the missing files are installed by another tool, please file a bug 
against it.
|  When filing the report, if the tool is not part of debhelper itself, please 
reference the
|  "Logging helpers and dh_missing" section from the "PROGRAMMING" guide for 
debhelper (10.6.3+).
|    (in the debhelper package: /usr/share/doc/debhelper/PROGRAMMING.gz)
|  Be sure to test with dpkg-buildpackage -A/-B as the results may vary when 
only a subset is built
|  If the omission is intentional or no other helper can take care of this 
consider adding the
|  paths to debian/not-installed.
| 
|  Remember to be careful with paths containing "x86_64-linux-gnu", where you 
might need to
|  use a wildcard or (assuming compat 13+) e.g. ${DEB_HOST_MULTIARCH} in 
debian/not-installed
|  to ensure it works on all architectures (see #961104).
| make: *** [debian/rules:24: binary-arch] Error 25
| dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit 
status 2

Helmut

Reply via email to