From: ludo@gnu.org (Ludovic Courtès)
To: Mark H Weaver <mhw@netris.org>
Cc: 22826@debbugs.gnu.org
Subject: bug#22826: gnupg test failure
Date: Tue, 01 Mar 2016 14:46:50 +0100 [thread overview]
Message-ID: <87h9gqnwdx.fsf@gnu.org> (raw)
In-Reply-To: <87bn6ztc0r.fsf@netris.org> (Mark H. Weaver's message of "Mon, 29 Feb 2016 16:57:56 -0500")
Mark H Weaver <mhw@netris.org> skribis:
> ludo@gnu.org (Ludovic Courtès) writes:
[...]
>> Isn’t it the same issue as
>> <http://debbugs.gnu.org/cgi/bugreport.cgi?bug=22558>? But that bug was
>> closed.
>
> It's true that the first message of bug 22558 mentioned two different
> failure modes of gnupg-2.1.11's test suite. However, the subsequent
> discussion focused on just one of those failure modes: the one that led
> to 14 test failures. I closed the bug when that failure mode was
> addressed.
Oh, I see.
> In retrospect, since these two failure modes have different causes and
> different fixes, perhaps I should have filed two separate bug reports
> from the beginning. If we can agree on this, then perhaps we can
> consider 22558 to address only the 14-test failure mode, and this bug
> (22826) can address the gpgtar.test failure mode.
>
> What do you think?
Makes sense, let’s keep it this way. We should probably retitle this
bug accordingly.
Thanks for the explanation,
Ludo’.
next prev parent reply other threads:[~2016-03-01 13:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-27 10:55 bug#22826: gnupg test failure Danny Milosavljevic
2016-02-27 13:18 ` Mark H Weaver
2016-02-28 15:51 ` Ludovic Courtès
2016-02-29 21:57 ` Mark H Weaver
2016-03-01 13:46 ` Ludovic Courtès [this message]
2018-02-05 22:14 ` Andreas Enge
2018-02-05 22:46 ` Leo Famulari
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=87h9gqnwdx.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=22826@debbugs.gnu.org \
--cc=mhw@netris.org \
/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/guix.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.