From: Julien Lepiller <julien@lepiller.eu>
To: Thomas Danckaert <post@thomasdanckaert.be>
Cc: help-guix@gnu.org
Subject: Re: very old daemon = no substitutes?
Date: Mon, 23 Dec 2019 13:14:25 +0100 [thread overview]
Message-ID: <20191223131425.10927375@sybil.lepiller.eu> (raw)
In-Reply-To: <20191223.125312.2027615464663329041.post@thomasdanckaert.be>
Le Mon, 23 Dec 2019 12:53:12 +0100 (CET),
Thomas Danckaert <post@thomasdanckaert.be> a écrit :
> Hi Guix,
>
> I'm reconfiguring my system after almost one year without updates
> (meaning guix-daemon in my system profile is at version
> 0.16.0-8.7ba2b27, dating from january 2019).
>
> I ran guix pull (now at commit c109d32) and had to rebuild *a lot*
> (guile, git, I believe multiple versions of gcc, ...). Now I'm
> reconfiguring, and it feels like I'm still building the whole world
> and not getting any substitutes (despite messages such as 'updating
> substitutes from https://ci.guix.info' and 'updating substitutes from
> https://berlin.guixsd.org')... could this be due to the old daemon,
> and should things improve once I have reconfigured a basic system
> with an up-do-date daemon, or is there something suspicious here?
>
> thank you for any help!
>
> Thomas
>
These two server names refer to the same machine, but I don't know if
the machine still serves substitutes on these names. Try using
https://ci.guix.gnu.org instead, and make sure you have authorized this
key:
https://git.savannah.gnu.org/cgit/guix.git/tree/etc/substitutes/berlin.guixsd.org.pub
next prev parent reply other threads:[~2019-12-23 12:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-23 11:53 very old daemon = no substitutes? Thomas Danckaert
2019-12-23 12:14 ` Julien Lepiller [this message]
2019-12-23 14:01 ` Ricardo Wurmus
2019-12-23 14:59 ` Thomas Danckaert
2019-12-23 15:28 ` Fwd: " Tobias Geerinckx-Rice
2019-12-23 18:56 ` Ricardo Wurmus
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=20191223131425.10927375@sybil.lepiller.eu \
--to=julien@lepiller.eu \
--cc=help-guix@gnu.org \
--cc=post@thomasdanckaert.be \
/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).