From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leo Famulari Subject: Re: How to "backport" a fix? Date: Thu, 18 Aug 2016 14:26:18 -0400 Message-ID: <20160818182618.GB20943@jasmine> References: <57B5D32E.1050702@crazy-compilers.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:57224) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1baS1S-0008IH-5D for guix-devel@gnu.org; Thu, 18 Aug 2016 14:26:35 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1baS1O-0007Hr-0a for guix-devel@gnu.org; Thu, 18 Aug 2016 14:26:33 -0400 Received: from out2-smtp.messagingengine.com ([66.111.4.26]:53059) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1baS1M-0007Gu-My for guix-devel@gnu.org; Thu, 18 Aug 2016 14:26:29 -0400 Content-Disposition: inline In-Reply-To: <57B5D32E.1050702@crazy-compilers.com> 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" To: Hartmut Goebel Cc: guix-devel On Thu, Aug 18, 2016 at 05:24:30PM +0200, Hartmut Goebel wrote: > Hi, > > thanks to Marius Bakke's tip django test run fine now -- except of two. > These are errors in the test-case which have been fixed just after the > release. > > What is the proper way to handle this? Include this fix as a patch? As a > snippet to the source? Or should I disable the two tests? If there are upstream patches that fix broken tests, then I think we should try taking those patches from upstream and applying them in the (source) field of the package. The patch files we use should include a brief comment explaining what they do (the upstream commit message might suffice) and a link to their source.