Re: Advice about GuixSD on Serveraptor?

[Leo Famulari]

On Wed, Mar 22, 2017 at 01:04:46PM +0100, Ricardo Wurmus wrote:
> Leo Famulari <address@hidden> writes:
> > 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.

Okay.

> 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?

It's not a bad idea to build it on Hydra. Hydra already builds a
usb-image / disk-image job [0], so we could add a qemu-image job, too.

I think that updates to the image would have to be handled manually. One
of us could send them a link to the new image and they'd make it
available to their users.

My expectation is that Serveraptor would offer our latest release, and
users would be expected to update their systems, as on bare-metal.

[0]
https://hydra.gnu.org/job/gnu/core-updates/usb-image.x86_64-linux