From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ricardo Wurmus Subject: Re: Advice about GuixSD on Serveraptor? Date: Wed, 22 Mar 2017 13:04:46 +0100 Message-ID: <87r31ptt41.fsf@elephly.net> References: <20170209183609.5rztohnqhsleifll@wasp> <20170213214717.GA11352@jasmine> <20170313003252.GA12094@jasmine> <20170321180638.GA3027@jasmine> <87mvcenzvw.fsf@dustycloud.org> <20170321204620.GA30143@jasmine> <20170321205335.GB30436@jasmine> 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]:45457) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cqf0b-0001xO-IN for guix-devel@gnu.org; Wed, 22 Mar 2017 08:04:58 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cqf0Y-0005Mh-E7 for guix-devel@gnu.org; Wed, 22 Mar 2017 08:04:57 -0400 Received: from sender-of-o51.zoho.com ([135.84.80.216]:21062) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1cqf0Y-0005MO-7U for guix-devel@gnu.org; Wed, 22 Mar 2017 08:04:54 -0400 In-reply-to: <20170321205335.GB30436@jasmine> 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: Leo Famulari Cc: guix-devel@gnu.org Leo Famulari writes: > On Tue, Mar 21, 2017 at 04:46:20PM -0400, Leo Famulari wrote: >> So what I'm doing here is trying to provide Serveraptor with a GuixSD >> image that they'd offer to users. >> >> People could regenerate the image themselves, but it would be difficult >> to verify that it matches what is offered by Serveraptor. > > And to clarify my previous question: Should this QEMU image be created > by me, or should it be created by a Guix maintainer as part of the Guix > release process? I’m not sure. I guess it would be better for users if it was signed by a maintainer key, but on the other hand I don’t know if we can commit to publishing QEMU images with every release. Could we build an image with Hydra instead and just provide the latest build to Serveraptor? How would updates to the image be handled? Do they offer some sort of API to upload new images or is this a process that depends on humans making decisions? -- Ricardo GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC https://elephly.net