From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leo Famulari Subject: Re: Test failure of ilmbase-2.2.0 on i686-linux (testBoxAlgo.cpp) Date: Tue, 8 Dec 2015 22:11:06 -0500 Message-ID: <20151209031106.GA11350@jasmine> References: <20151208053857.GA29923@jasmine> <87d1ug98fi.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:35821) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a6V9u-0000ca-6a for guix-devel@gnu.org; Tue, 08 Dec 2015 22:11:15 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1a6V9p-0003f4-OH for guix-devel@gnu.org; Tue, 08 Dec 2015 22:11:14 -0500 Received: from out4-smtp.messagingengine.com ([66.111.4.28]:45047) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a6V9p-0003ee-LF for guix-devel@gnu.org; Tue, 08 Dec 2015 22:11:09 -0500 Content-Disposition: inline In-Reply-To: <87d1ug98fi.fsf@gnu.org> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org To: Ludovic =?iso-8859-1?Q?Court=E8s?= Cc: Guix-devel On Tue, Dec 08, 2015 at 06:06:25PM +0100, Ludovic Courtès wrote: > Hi Leo, and thanks for the perfect upstream bug report! > > Leo Famulari skribis: > > > [1] > > http://lists.gnu.org/archive/html/bug-guix/2015-11/msg00179.html > > Small comment: bug-guix@gnu.org is linked to the bug tracker at > . It is best to refer to the bug by canonical > URL, in this case, and to Cc: > 22049@debbugs.gnu.org, so we keep track of the discussion. D'oh! I made a note of this practice in the past but it slipped my mind. > > I reckon this is probably not obvious to someone who hasn’t used > bugs.gnu.org before; maybe we should fix our documentation? It's a good idea, especially for new packagers like me. I suppose under packaging there could be a brief description of how to write a good bug report in general as well as Guix-specific things like how to reference the bug. As well as a reminder to practice rubber-duck debugging before sending the bug report ;) > > Thanks again, > Ludo’.