From: zimoun <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: guix weather -m etc/sources-manifest.scm and CI?
Date: Thu, 23 Sep 2021 22:36:13 +0200 [thread overview]
Message-ID: <86h7eb58si.fsf@gmail.com> (raw)
In-Reply-To: <87a6k39hc1.fsf@gnu.org>
Hi,
On Thu, 23 Sep 2021 at 22:18, Ludovic Courtès <ludo@gnu.org> wrote:
> BTW, I meant to send a message here about these two manifests
Sorry if I shot your surprise effect announcement. :-)
> I set up a Cuirass job the other day¹, but due to my aforementioned
> disorganization, I haven’t yet taken the time to investigate its
> failure.
>
> ¹ https://ci.guix.gnu.org/jobset/source
Cool!
(Find my stuff with Cuirass always requires magic for me :-))
>> Does it make sense to duplicate the storage of all these origins?
>
> It surely does.
Do you mean having all twice: on Berlin and Bordeaux. In addition to SWH
(although it is not ready yet).
>> PS: about etc/disarchive-manifest.scm, I guess 'all-origins' is missing:
> No, there’s:
>
> (include "source-manifest.scm")
>
> at the top.
Oops!
> So the goal here was to move forward on this front by (1) setting up a
> CI jobset, and (2) having an mcron job or something that would
> periodically copy the “disarchives” in a directory served by nginx. We
> have had all the code and most of the infrastructure for several months,
> so I thought it’s high time to get our act together. Help welcome!
Thanks for pushing forward. :-)
Cheers,
simon
next prev parent reply other threads:[~2021-09-23 20:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-15 17:03 guix weather -m etc/sources-manifest.scm and CI? zimoun
2021-09-17 9:49 ` Christopher Baines
2021-09-21 8:32 ` zimoun
2021-09-21 20:36 ` Christopher Baines
2021-09-23 20:18 ` Ludovic Courtès
2021-09-23 20:36 ` zimoun [this message]
2021-09-28 12:28 ` Ludovic Courtès
2021-10-01 9:38 ` Mathieu Othacehe
2021-10-02 14:48 ` Ludovic Courtès
2021-10-02 17:08 ` Mathieu Othacehe
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=86h7eb58si.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
/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.