From: Andreas Enge <andreas@enge.fr>
To: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
Cc: help-guix@gnu.org, Adrien 'neox' Bourmault <neox@a-lec.org>,
Jason Self <j@jxself.org>
Subject: Re: Guix 1.4.0+i686: getting ghc substitutes?
Date: Fri, 25 Oct 2024 11:17:12 +0200 [thread overview]
Message-ID: <ZxtiGAutkchMFfey@jurong> (raw)
In-Reply-To: <20241024163233.586b31ec@primary_laptop>
Hello Denis,
Am Thu, Oct 24, 2024 at 04:32:33PM +0200 schrieb Denis 'GNUtoo' Carikli:
> And so I end up being able to download these:
> > $ guix build \
> > --substitute-urls=https://bordeaux.guix.gnu.org \
> > --system=i686-linux \
> > pandoc
> > [...]
> > substituting
this looks as if you are using too old a Guix daemon; more recent versions
enable the Bordeaux build farm by default.
We should do a release :)
Andreas
next prev parent reply other threads:[~2024-10-25 9:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-18 20:26 Guix 1.4.0+i686: getting ghc substitutes? Denis 'GNUtoo' Carikli
2024-10-24 14:32 ` Denis 'GNUtoo' Carikli
2024-10-25 9:17 ` Andreas Enge [this message]
2024-10-26 16:33 ` Denis 'GNUtoo' Carikli
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZxtiGAutkchMFfey@jurong \
--to=andreas@enge.fr \
--cc=GNUtoo@cyberdimension.org \
--cc=help-guix@gnu.org \
--cc=j@jxself.org \
--cc=neox@a-lec.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).