From: ludo@gnu.org (Ludovic Courtès)
To: Niall Dooley <dooleyn@gmail.com>
Cc: Alex Kost <alezost@gmail.com>, help-guix <Help-Guix@gnu.org>
Subject: Re: Unable to use Aspell installed via Guix
Date: Tue, 09 May 2017 10:36:13 +0200 [thread overview]
Message-ID: <87shkea0le.fsf@gnu.org> (raw)
In-Reply-To: <CADS3Lq69g0UGDYFpAyeWaC8XLgxySTLgZuesqdVTAUGTFcvp-A@mail.gmail.com> (Niall Dooley's message of "Sat, 6 May 2017 22:24:35 +0200")
Hi Niall,
Niall Dooley <dooleyn@gmail.com> skribis:
> [21:06 doolio@mars ~] > guix package -i aspell-dict-en
> The following package will be installed:
> aspell-dict-en 2016.11.20-0
> /gnu/store/0krzlail39f8lf58bnm0jwvrr0sb0f8s-aspell-dict-en-2016.11.20-0
>
> The following derivations will be built:
> /gnu/store/g9qgdjdx29km0njjnsbfynnc4s6if046-profile.drv
> /gnu/store/wpjssm1mq5yw568gl53vkzg3brlpn7fz-ca-certificate-bundle.drv
> /gnu/store/wb92jkdz04x0s7q00dpykx6b49p19nil-gtk-im-modules.drv
> /gnu/store/m50w7gsvqffbshppfz6a0np24b3lmih6-fonts-dir.drv
> /gnu/store/k5v6ly8x6lbzqx32nkw9698ndzpwg50m-gtk-icon-themes.drv
> /gnu/store/k38q4ykbj7dqmp0cimqg7b85dljjbpvy-info-dir.drv
> /gnu/store/0avf60c7la7q3wssp1q8w1vsfb4jcr1v-xdg-mime-database.drv
> /gnu/store/p4gi1clp3nhaii069rp2f0pvq8qcnd53-manual-database.drv
> The following file will be downloaded:
> /gnu/store/0krzlail39f8lf58bnm0jwvrr0sb0f8s-aspell-dict-en-2016.11.20-0
> Downloading https://mirror.hydra.gnu.org/guix/nar/gzip/0krzlail39f8lf58bnm0jwvrr0sb0f8s-aspell-dict-en-2016.11.20-0
> (4.1MiB installed)...
> guix substitute: error: download from
> 'https://mirror.hydra.gnu.org/guix/nar/gzip/0krzlail39f8lf58bnm0jwvrr0sb0f8s-aspell-dict-en-2016.11.20-0'
> failed: 404, "Not Found"
> guix package: error: build failed: some substitutes for the outputs of
> derivation `/gnu/store/0xq6hspp0xqvxnb7mqlj3phpf3m14k7g-aspell-dict-en-2016.11.20-0.drv'
> failed (usually happens due to networking issues); try `--fallback' to
> build derivation from source
Apologies for this. The problem was due to the combination of two
issues: a change in how we publish substitutes (see
<https://debbugs.gnu.org/cgi/bugreport.cgi?bug=26201#96>), and a
misconfiguration of nginx at mirror.hydra.gnu.org, which led it to cache
meta-data (“narinfos”) for too long, in turn leading to the above
discrepancy (the mirror thinks it has aspell-dict-en when in fact all it
has is its meta-data).
I believe the latter is addressed by
<https://git.savannah.gnu.org/cgit/guix/maintenance.git/commit/?id=422a350d6b3e3b5b9f73a417aecf7be41510842c>,
though it could take a few days to “refresh” the cache.
At any rate, please let us know if you still experience 404s like this.
The workaround in the meantime is --fallback.
Thanks,
Ludo’.
next prev parent reply other threads:[~2017-05-09 8:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-06 13:49 Unable to use Aspell installed via Guix Niall Dooley
2017-05-06 19:22 ` Alex Kost
2017-05-06 20:24 ` Niall Dooley
2017-05-06 20:32 ` Leo Famulari
2017-05-07 11:58 ` Niall Dooley
2017-05-07 19:27 ` Leo Famulari
2017-05-09 8:36 ` Ludovic Courtès [this message]
[not found] ` <CADS3Lq6VYL7gBmqNUEZhGvYFAHgF1fzhUw4Ojhgua8V=h9zi5Q@mail.gmail.com>
2017-05-15 9:54 ` Ludovic Courtès
2017-05-24 18:52 ` Niall Dooley
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=87shkea0le.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=Help-Guix@gnu.org \
--cc=alezost@gmail.com \
--cc=dooleyn@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.
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).