|
From: | Dmitry Gutov |
Subject: | bug#23513: package.el treats empty signatures as correct |
Date: | Mon, 16 May 2016 23:19:37 +0300 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.1 |
On 05/16/2016 09:39 PM, Glenn Morris wrote:
That's definitely a cause for concern. Glenn, does Hydra lack the necessary libraries to support the package signature check?Hydra's "gnupg" package is from the 2.0 series, and only provides a "gpg2" executable. epg-config--program-alist requires something from the 2.1 series. So (epg-find-configuration 'OpenPGP) fails with "no usable configuration". I have added "gnupg1" to the requirements for the coverage build in an effort to get a "gpg" executable. We'll see if this helps.
Thanks.Ideally, we'd have something like (skip-unless (or (getenv "HYDRA") (ignore-errors ...)), to make sure the tests like that are _not_ skipped on the CI.
Individual contributors may not have gpg installed (although there's a case to be made that the package tests should just fail for them), but the CI is our last "line of defense", especially for important tests.
(It would be easier to see if this worked if the coverage job wasn't currently failing, as it has been for two weeks, due to network-stream changes that cause a test failure - bug#23508. This is a repeated pattern that makes me think people don't actually pay much attention to the coverage job.)
I've noticed this failure when running tests locally, but it's far from my area of expertise.
I think using a separate mailing list for the build status notifications might be a mistake. I'm not subscribed to it (not sure why; maybe I've missed the announcement), and apparently not many other people are.
There's not a lot traffic there, why not just send it to emacs-devel?
[Prev in Thread] | Current Thread | [Next in Thread] |