[request-tracker-maintainers] Bug#988905: src:request-tracker5: ftbfs due to changes in gpg error messages

Andrew Ruthven andrew at etc.gen.nz
Fri May 21 10:06:02 BST 2021


Hi Michael,

Thanks for the report.

On Fri, 2021-05-21 at 14:45 +1200, Michael Hudson-Doyle wrote:
> The failures are:
> 
> #   Failed test at t/mail/crypt-gnupg.t line 171.
> # found warning: gpg: error retrieving 'keyless at example.com' via WKD:
> Server indicated a failure
> # expected to find warning: (?^:public key not found|error retrieving
> 'keyless\@example.com' via WKD: No data)
> 
> #   Failed test at t/web/crypt-gnupg.t line 358.
> # found warning: gpg: error retrieving 'nokey at example.com' via WKD:
> Server indicated a failure

After a little bit of digging I am able to reproduce this error, but it
requires disabling the use of DNS nameservers by my resolver. It seems
that "Server indicated a failure" is returned if DNS fails.

> (the messages are actually slightly different in Ubuntu). This seems
> pretty benign really and probably the tests should be relaxed?

I wonder if the tests should just disable WKD lookup to find missing
keys and rely on local only.

This also has the benefit of not needing working networking to do a
build.

What do you think?

Cheers,
Andrew

-- 
Andrew Ruthven, Wellington, New Zealand
andrew at etc.gen.nz         |
Catalyst Cloud:           | This space intentionally left blank
 https://catalystcloud.nz |





More information about the pkg-request-tracker-maintainers mailing list