all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Mathieu Othacehe <m.othacehe@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Building guix-modular with cuirass
Date: Mon, 30 Apr 2018 15:04:33 +0200	[thread overview]
Message-ID: <87po2gyhem.fsf@gnu.org> (raw)
In-Reply-To: <87a7tpc8vw.fsf@gmail.com> (Mathieu Othacehe's message of "Fri, 27 Apr 2018 11:10:27 +0200")

Hello Mathieu,

Mathieu Othacehe <m.othacehe@gmail.com> skribis:

> I setup my own cuirass server to build guix-modular, here's how:
>
> (define (build-guix-modular store arguments)

You shouldn’t need to do anything like that.  Here’s what we have on
berlin.guixsd.org:

--8<---------------cut here---------------start------------->8---
$ sudo sqlite3 /var/run/cuirass/cuirass.db 
SQLite version 3.19.3 2017-06-08 14:26:16
Enter ".help" for usage hints.
sqlite> select * from specifications where repo_name='guix-modular';
guix-modular|https://git.savannah.gnu.org/git/guix.git||build-aux/cuirass/guix-modular.scm|cuirass-jobs|((systems "x86_64-linux" "i686-linux" "aarch64-linux"))|master|||1
--8<---------------cut here---------------end--------------->8---

If you add a similar entry on your server, it should be fine.

Can you try and report back?

If Cuirass doesn’t seem to do what you want, I recommend browsing
/var/log/cuirass.log to see what’s going on.

HTH!

Ludo’.

  reply	other threads:[~2018-04-30 13:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-27  9:10 Building guix-modular with cuirass Mathieu Othacehe
2018-04-30 13:04 ` Ludovic Courtès [this message]
2018-04-30 18:29   ` Mathieu Othacehe
2018-05-01 20:56     ` Ludovic Courtès
2018-05-02 13:52       ` Mathieu Othacehe
2018-05-09 22:05         ` Ludovic Courtès
2018-05-08 21:23       ` Nils Gillmann
2018-05-13  2:17         ` Chris Marusich
2018-05-13  7:48           ` swedebugia

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87po2gyhem.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=help-guix@gnu.org \
    --cc=m.othacehe@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.