From: Artur Malabarba <bruce.connor.am@gmail.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: Mark Oteiza <mvoteiza@udel.edu>,
22440@debbugs.gnu.org, Dmitry Gutov <dgutov@yandex.ru>
Subject: bug#22440: 25.1.50; package.el fails to install with package-check-signature t
Date: Wed, 18 May 2016 20:43:58 +0000 [thread overview]
Message-ID: <CAAdUY-KU6PNzrq89Lmfpa9YJrHjkvcqk_fV9s+P7VULCUDa9mw@mail.gmail.com> (raw)
In-Reply-To: <87futf6tjj.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 581 bytes --]
How do we run tests for a single file with the new test structure? I use to
call `make package-test` inside the test/automated directory. But I can't
seem to find an equivalent with the new structure.
On Wed, May 18, 2016 at 4:43 PM Artur Malabarba <bruce.connor.am@gmail.com>
wrote:
> Artur Malabarba <bruce.connor.am@gmail.com> writes:
>
> > I couldn't reproduce this, so it might have been fixed already.
> > Mark, could you check if this has been fixed for you?
>
> Given the other information provided on this thread, I can indeed
> reproduce this now. I'll look into it.
>
[-- Attachment #2: Type: text/html, Size: 936 bytes --]
next prev parent reply other threads:[~2016-05-18 20:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-23 0:48 bug#22440: 25.1.50; package.el fails to install with package-check-signature t Mark Oteiza
2016-05-15 7:03 ` Paul Eggert
2016-05-15 11:32 ` Dmitry Gutov
2016-05-15 16:50 ` Paul Eggert
2016-05-16 10:59 ` Artur Malabarba
2016-05-18 13:50 ` Artur Malabarba
2016-05-18 16:29 ` Mark Oteiza
2016-05-18 16:36 ` Dmitry Gutov
2016-05-18 16:44 ` Mark Oteiza
2016-05-18 18:10 ` Paul Eggert
2016-05-18 18:23 ` Dmitry Gutov
2016-05-18 19:24 ` Artur Malabarba
2016-05-18 19:33 ` Artur Malabarba
2016-05-19 1:30 ` Daiki Ueno
2016-05-18 19:43 ` Artur Malabarba
2016-05-18 20:43 ` Artur Malabarba [this message]
2016-05-18 21:09 ` Artur Malabarba
2016-05-18 22:05 ` Paul Eggert
2016-05-18 23:11 ` Artur Malabarba
2016-05-19 15:15 ` Paul Eggert
2016-05-19 4:39 ` Lizzie Dixon
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAAdUY-KU6PNzrq89Lmfpa9YJrHjkvcqk_fV9s+P7VULCUDa9mw@mail.gmail.com \
--to=bruce.connor.am@gmail.com \
--cc=22440@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=eggert@cs.ucla.edu \
--cc=mvoteiza@udel.edu \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).