From: Glenn Morris <rgm@gnu.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: 23513@debbugs.gnu.org, "L. Dixon" <_@lizzie.io>
Subject: bug#23513: package.el treats empty signatures as correct
Date: Mon, 16 May 2016 14:39:19 -0400 [thread overview]
Message-ID: <1rvb2dx2y0.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <b5102cbd-e75b-8bdd-2923-45cb2fc593a4@yandex.ru> (Dmitry Gutov's message of "Sun, 15 May 2016 00:38:30 +0300")
Dmitry Gutov wrote:
> On 05/11/2016 12:39 PM, L. Dixon wrote:
>
>> I also deleted the skip-unless clause in the package-test-signed,
>> since the test runs normally without it. I may be misunderstanding
>> something here, but I'm worried that skipping this test will mask
>> similar issues or regressions.
No, that stuff is there for a reason. Please don't delete it just
becauses it's not needed on your system.
> 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.
(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.)
next prev parent reply other threads:[~2016-05-16 18:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-11 9:39 bug#23513: package.el treats empty signatures as correct L. Dixon
2016-05-14 1:49 ` Paul Eggert
2016-05-14 21:38 ` Dmitry Gutov
2016-05-16 18:39 ` Glenn Morris [this message]
2016-05-16 20:19 ` Dmitry Gutov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1rvb2dx2y0.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=23513@debbugs.gnu.org \
--cc=_@lizzie.io \
--cc=dgutov@yandex.ru \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.