Bug#839580: request-tracker4: FTBFS in testing (failed tests)

[Niko Tyni]

Control: tag -1 help

On Sun, Oct 02, 2016 at 10:42:49AM +0000, Santiago Vila wrote:
> Package: src:request-tracker4
> Version: 4.2.13-2
> Severity: serious

> t/mail/gnupg-outgoing-signed_encrypted.t             (Wstat: 3584 Tests: 68 Failed: 14)
>   Failed tests:  10-11, 18-19, 27-28, 35-36, 41, 43, 48
>                 50, 67-68
>   Non-zero exit status: 14
>   Parse errors: Bad plan.  You planned 104 tests but ran 68.
> t/mail/gnupg-special.t                               (Wstat: 512 Tests: 19 Failed: 2)
>   Failed tests:  16, 19
>   Non-zero exit status: 2
>   Parse errors: Bad plan.  You planned 26 tests but ran 19.

[...]

All this regressed with libgnupg-interface-perl_0.52-4. Presumably the
test suite now exercises gnupg2 instead of gnupg1 for the parts using
GnuPG::Interface (= most of the actual GnuPG related functionality.)

There seem to be at least hardcoded gnupg error messages in the test
suite that probably need changing:

  like( $warnings[0], qr{signing failed: secret key not available},

Not sure if RT::Crypt::GnuPG is going to require some porting too.

Help untangling this mess would be very welcome, as both Dominic and I
are rather short on time. Tagging and copying possible candidates :)

(BTW there's also a missing build dependency on tzdata that can create
additional failures for clean chroots.)
-- 
Niko Tyni   ntyni at debian.org