Source: request-tracker4 Version: 4.4.4-1 Severity: serious Tags: ftbfs X-Debbugs-Cc: libgnupg-interface-p...@packages.debian.org
This package fails its test suite with libgnupg-interface-perl_1.00-1, which recently entered sid. Many (but not all) of the test suite failures seem to be about gpg: Invalid option "--pinentry-mode" The build hangs in the end. I assume this needs to be fixed in request-tracker4 rather than libgnupg-interface-perl, but feel free to reassign of course. Some excerpts: # Failed test 'encrypted attachment' # at t/crypt/gnupg/attachments-in-db.t line 38. # Failed test 'correct content' # at t/crypt/gnupg/attachments-in-db.t line 40. # got: 'test' # expected: anything else # Failed test 'no warnings' # at /usr/share/perl/5.30/Test/Builder.pm line 152. # There were 3 warning(s) # Previous test 0 '' # gpg: Invalid option "--pinentry-mode" [...] # Failed test 'has key info.' # at t/mail/gnupg-bad.t line 20. # got: "<!DOCTYPE html>\x{0a}\x{0a}<html lang="en">\x{0a} <head>\x{0a} <ti"... # length: 27792 # doesn't match '(?^:rt\@example.com.* - never)' # Dumped failing test page content to /<<PKGBUILDDIR>>/t/tmp/mail-gnupg-bad.t-Vm133E7R/3-Modify.html # Failed test 'no warnings emitted' # at /<<PKGBUILDDIR>>/lib/RT/Test/Web.pm line 483. # got: '1' # expected: '0' # got warning: gpg: Invalid option "--pinentry-mode" # Some tests failed or we bailed out, tmp directory '/<<PKGBUILDDIR>>/t/tmp/mail-gnupg-bad.t-Vm133E7R' is not cleaned # Looks like you failed 2 tests of 8. t/mail/gnupg-bad.t ..................................... Dubious, test returned 2 (wstat 512, 0x200) and so forth. -- Niko Tyni nt...@debian.org