Source: cryptsetup Version: 2.3.3-1 Severity: normal >From my sbuild log:
... checking for systemd tmpfiles config directory... /usr/lib/tmpfiles.d ... dh_missing -a dh_missing: warning: usr/lib/tmpfiles.d/cryptsetup.conf exists in debian/tmp but is not installed to anywhere (related file: "scripts/cryptsetup.conf") dh_missing: error: missing files, aborting Some of the files had a file that looked similar to a missing counter part. Perhaps one of the debhelper tools should installed the missing file instead of its related file assuming the content is identical. As an example, perhaps you want to replace: * scripts/cryptsetup.conf with: * usr/lib/tmpfiles.d/cryptsetup.conf 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: cryptsetup (19), cryptsetup-bin (27), cryptsetup-initramfs (15), cryptsetup-run (0), cryptsetup-udeb (16), libcryptsetup-dev (3), libcryptsetup12 (2), libcryptsetup12-udeb (2) * dh_installdocs: cryptsetup (53), cryptsetup-bin (0), cryptsetup-initramfs (1), cryptsetup-run (0), libcryptsetup-dev (1), libcryptsetup12 (0) * dh_installexamples: cryptsetup (1), cryptsetup-bin (0), cryptsetup-initramfs (0), cryptsetup-run (0), libcryptsetup-dev (0), libcryptsetup12 (0) * dh_installman: cryptsetup (4), cryptsetup-bin (0), cryptsetup-initramfs (0), cryptsetup-run (0), libcryptsetup-dev (0), libcryptsetup12 (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 For a short-term work-around: Add the files to debian/not-installed make: *** [debian/rules:19: binary-arch] Error 25 dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit status 2 I do have systemd installed in my chroot image, since I'm using a custom version of sbuild with a backend using systemd-nspawn to start up a container to build in. -- Daniel Schepler