From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark H Weaver Subject: bug#24833: Hydra ignores MIPS-specific patch for Mesa on core-updates Date: Wed, 02 Nov 2016 22:10:50 -0400 Message-ID: <87eg2ttis5.fsf@netris.org> References: <87ins5le6d.fsf@gnu.org> <87shrdca9s.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]:48436) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1c27Wb-0000m5-P0 for bug-guix@gnu.org; Wed, 02 Nov 2016 22:13:06 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1c27WY-0006d4-Iv for bug-guix@gnu.org; Wed, 02 Nov 2016 22:13:05 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:53879) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1c27WY-0006ct-Fd for bug-guix@gnu.org; Wed, 02 Nov 2016 22:13:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1c27WY-0000vT-8H for bug-guix@gnu.org; Wed, 02 Nov 2016 22:13:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <87ins5le6d.fsf@gnu.org> 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" To: Ludovic =?UTF-8?Q?Court=C3=A8s?= Cc: 24833@debbugs.gnu.org ludo@gnu.org (Ludovic Court=C3=A8s) > Mark H Weaver skribis: > >> Commit f1267c872fcaed6c53d43b3ff51abb726f7418d6 on core-updates added a >> patch to Mesa on MIPS only, in order to prevent unnecessary rebuilds on >> other systems. 'guix' running on a MIPS system generates a derivation >> that applies the patch, but the derivation generated for MIPS on Hydra >> omits the patch. > > Did it turn out to be the same issue as , or > is it something entirely different? Bug 24833 is this bug, so yes, by reflexivity it's the same issue, but I suspect that's not what you meant to ask :) This bug still remains, and I'm not aware of another bug that's the same issue as this one. Thanks, Mark