Package: dpkg-dev Version: 1.19.0.5 Severity: normal For explicit triggers, both the interested and activated packages can specify "await" or "noawait". I could not understand from the current documentation what is supposed to happen if the two specify the opposite.
Looking at the source, I think that the triggering package will only await the trigger if both specify "await" (or don't specify either way). Ben. -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.17.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages dpkg-dev depends on: ii binutils 2.31-1 ii bzip2 1.0.6-8.1 ii libdpkg-perl 1.19.0.5 ii make 4.2.1-1.1 ii patch 2.7.6-2 ii perl 5.26.2-6 ii tar 1.30+dfsg-2 ii xz-utils 5.2.2-1.3 Versions of packages dpkg-dev recommends: ii build-essential 12.5 ii clang-4.0 [c-compiler] 1:4.0.1-10+b1 ii clang-6.0 [c-compiler] 1:6.0.1-2 ii fakeroot 1.23-1 ii gcc [c-compiler] 4:7.3.0-3 ii gcc-4.8 [c-compiler] 4.8.5-4 ii gcc-7 [c-compiler] 7.3.0-26 ii gnupg 2.2.8-3 ii gnupg2 2.2.8-3 ii gpgv 2.2.8-3 ii libalgorithm-merge-perl 0.08-3 Versions of packages dpkg-dev suggests: ii debian-keyring 2018.06.24 -- no debconf information
