From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?UTF-8?Q?Court=C3=A8s?=) Subject: bug#32575: [Cuirass] Filter results by architecture Date: Thu, 30 Aug 2018 14:14:07 +0200 Message-ID: <87efegxd9s.fsf@gnu.org> References: <87a7p5b7x3.fsf@elephly.net> <20180830114135.3226977f@scratchpost.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]:39885) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fvLxw-0002qk-1I for bug-guix@gnu.org; Thu, 30 Aug 2018 08:22:27 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fvLqp-0002LC-53 for bug-guix@gnu.org; Thu, 30 Aug 2018 08:15:07 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:32991) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fvLqo-0002Ks-6N for bug-guix@gnu.org; Thu, 30 Aug 2018 08:15:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1fvLqn-0003yn-TX for bug-guix@gnu.org; Thu, 30 Aug 2018 08:15:01 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <20180830114135.3226977f@scratchpost.org> (Danny Milosavljevic's message of "Thu, 30 Aug 2018 11:41:35 +0200") 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: Danny Milosavljevic Cc: 32575@debbugs.gnu.org, clement@lassieur.org Hi Danny & all, Danny Milosavljevic skribis: > I think that for a portable package, the architecture it runs on is > an implementation detail - it should build on all of them. If it doesn't, > that should show up as an error. > > So I had > > hello [x86_64-checkbox-log] [armhf-checkbox-log] [aarch64-checkbox= -log] > > and not > > hello.x86_64 [checkbox-log] > hello.armhf [checkbox-log] > hello.aarch64 [checkbox-log] > > The latter looks more like these are different packages with different pu= rposes - > which they really aren't from a user standpoint. The difficulty is that, from Cuirass=E2=80=99 viewpoint, =E2=80=9Chello.x86= _64-linux=E2=80=9D and =E2=80=9Chello.armhf-linux=E2=80=9D are just two different unrelated jo= bs. Perhaps what we would need is to internally change how jobs are represented in the database: we could have one job, =E2=80=9Chello=E2=80=9D= , connected to one or more =E2=80=9Cbuilds=E2=80=9D, each with its own system. I think it would amount to splitting the =E2=80=9CBuilds=E2=80=9D table int= o two tables: =E2=80=9CBuilds=E2=80=9D and =E2=80=9CJobs=E2=80=9D. Cl=C3=A9ment, does th= at make sense? Ludo=E2=80=99.