From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark H Weaver Subject: bug#33676: GuixSD on eoma68-a20? Date: Sat, 08 Dec 2018 15:59:58 -0500 Message-ID: <87pnubn386.fsf__6416.49377435005$1544302815$gmane$org@netris.org> References: <68f9fc17-94f5-dcc2-f54d-61d6e2bf384d@riseup.net> <20181208181214.2308472a@scratchpost.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:52816) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gVjjj-0001Ho-7l for bug-guix@gnu.org; Sat, 08 Dec 2018 16:02:07 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gVjjg-0005Rs-0U for bug-guix@gnu.org; Sat, 08 Dec 2018 16:02:07 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:34559) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gVjjf-0005Rm-Sw for bug-guix@gnu.org; Sat, 08 Dec 2018 16:02:03 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1gVjje-0004mb-1B for bug-guix@gnu.org; Sat, 08 Dec 2018 16:02:03 -0500 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <20181208181214.2308472a@scratchpost.org> (Danny Milosavljevic's message of "Sat, 8 Dec 2018 18:12:14 +0100") 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: guix-devel@gnu.org, 33676@debbugs.gnu.org Hi Danny, Danny Milosavljevic writes: > On Sat, 8 Dec 2018 17:39:01 +0100 > swedebugia wrote: > >> Could we pre-order some of these owned by the foundation to >> be used to to hack on this? >> >> See https://www.crowdsupply.com/eoma68/micro-desktop > > Guix received one but we have so far be unable to get the GuixSD flash > image because something always breaks on Hydra before it's done (for > example lack of disk space - see https://hydra.gnu.org/build/3198097/log/raw . > Note: The latter thing counts as "successful" build. WTF?). This sounds like two distinct bugs: * Regarding the lack of disk space: if I'm not mistaken, as things are currently implemented, we must specify the size of the disk image manually. I guess we need to increase the size. * This error that occurs within QEMU is apparently not being propagated to the outer build script. That should be fixed. > I'm now setting up my own build server and trying to get the flash image > that way - which is ridiculous. You seem to be assuming that the problem building the disk image is a Hydra-specific problem. Do you have reason to believe so? I would guess that these bugs are in the disk image builder. What do you think? Regards, Mark