Lucas Nussbaum <lu...@debian.org> writes: > Source: notmuch > Version: 0.22.1-3 > Severity: serious > Tags: stretch sid > User: debian...@lists.debian.org > Usertags: qa-ftbfs-20160906 qa-ftbfs > Justification: FTBFS on amd64 > > Hi, > > During a rebuild of all packages in sid, your package failed to build on > amd64. > > > The full build log is available from: > > http://people.debian.org/~lucas/logs/2016/09/06/notmuch_0.22.1-3_unstable.log
It doesn't seem to be there? In any case I think I can reproduce at least some of the failures locally; it seems to related to changes in the output of gpg --no-tty --list-secret-keys --with-colons --fingerprint introduced by gnupg 2.1.15 The failures I can reproduce are fixed by diff --git a/test/T350-crypto.sh b/test/T350-crypto.sh index 3656cce..5a63183 100755 --- a/test/T350-crypto.sh +++ b/test/T350-crypto.sh @@ -26,7 +26,7 @@ add_gnupg_home () add_gnupg_home # get key fingerprint -FINGERPRINT=$(gpg --no-tty --list-secret-keys --with-colons --fingerprint | grep '^fpr:' | cut -d: -f10) +FINGERPRINT=$(gpg --no-tty --list-secret-keys --with-colons --fingerprint | grep '^fpr:' | cut -d: -f10 |head -1) test_expect_success 'emacs delivery of signed message' \ 'emacs_fcc_message \ I'll have to think about whether this is the most robust fix possible; I'd like to avoid future breakage caused by gpg changing --with-colons output.