Package: cryptsetup Version: 2:2.0.0-1 Severity: normal You currently just run autoreconf -f -i instead of using dh_autoreconf there and dh_autoreconf_clean in clean, meaning the source package cannot be built again once you started building binaries because files have changed and new files appeared.
-- Package-specific info: -- System Information: Debian Release: buster/sid APT prefers bionic APT policy: (500, 'bionic'), (100, 'bionic-proposed') Architecture: amd64 (x86_64) Kernel: Linux 4.13.0-30-generic (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages cryptsetup depends on: ii cryptsetup-bin 2:2.0.1-0ubuntu1 ii debconf [debconf-2.0] 1.5.65 ii dmsetup 2:1.02.145-4.1ubuntu1 ii libc6 2.26-0ubuntu2 Versions of packages cryptsetup recommends: ii busybox-static [busybox] 1:1.27.2-2ubuntu3 ii console-setup 1.166ubuntu7 ii initramfs-tools [linux-initramfs-tool] 0.130ubuntu1 ii kbd 2.0.4-2ubuntu1 ii plymouth 0.9.3-1ubuntu1 Versions of packages cryptsetup suggests: ii dosfstools 4.1-1 ii keyutils 1.5.9-9.2ubuntu1 ii liblocale-gettext-perl 1.07-3build2 -- debconf information excluded -- debian developer - deb.li/jak | jak-linux.org - free software dev ubuntu core developer i speak de, en
