From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?UTF-8?Q?Court=C3=A8s?=) Subject: bug#22826: gnupg test failure Date: Tue, 01 Mar 2016 14:46:50 +0100 Message-ID: <87h9gqnwdx.fsf@gnu.org> References: <20160227115539.49203a2a@scratchpost.org> <87egbythp5.fsf@netris.org> <87r3fwx27n.fsf@gnu.org> <87bn6ztc0r.fsf@netris.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:60550) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aakel-0002M3-16 for bug-guix@gnu.org; Tue, 01 Mar 2016 08:48:10 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aakeg-0007Yt-9h for bug-guix@gnu.org; Tue, 01 Mar 2016 08:48:06 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:57709) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aakeg-0007Yp-6e for bug-guix@gnu.org; Tue, 01 Mar 2016 08:48:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84) (envelope-from ) id 1aakeg-0007rk-1f for bug-guix@gnu.org; Tue, 01 Mar 2016 08:48:02 -0500 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <87bn6ztc0r.fsf@netris.org> (Mark H. Weaver's message of "Mon, 29 Feb 2016 16:57:56 -0500") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org To: Mark H Weaver Cc: 22826@debbugs.gnu.org Mark H Weaver skribis: > ludo@gnu.org (Ludovic Court=C3=A8s) writes: [...] >> Isn=E2=80=99t it the same issue as >> ? 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=E2=80=99s keep it this way. We should probably retitle th= is bug accordingly. Thanks for the explanation, Ludo=E2=80=99.