From: ludo@gnu.org (Ludovic Courtès)
To: Mathieu Lirzin <mthl@gnu.org>
Cc: 30157-done@debbugs.gnu.org
Subject: bug#30157: texlive-20170524-texmf.tar.xz' failed: 410, "Gone"
Date: Fri, 19 Jan 2018 14:22:34 +0100 [thread overview]
Message-ID: <87lggu56g5.fsf@gnu.org> (raw)
In-Reply-To: <87y3kvtjku.fsf@gnu.org> (Mathieu Lirzin's message of "Thu, 18 Jan 2018 13:52:49 +0100")
Mathieu Lirzin <mthl@gnu.org> skribis:
> Téléchargement de « https://mirror.hydra.gnu.org/guix/nar/5rnvmy02yazy8iwaa91kijbbqp8qmflz-texlive-20170524-texmf.tar.xz »...
> guix substitute: error: download from 'https://mirror.hydra.gnu.org/guix/nar/5rnvmy02yazy8iwaa91kijbbqp8qmflz-texlive-20170524-texmf.tar.xz' failed: 410, "Gone"
Fixed by simply letting it through:
https://git.savannah.gnu.org/cgit/guix/maintenance.git/commit/?id=8859af255f4041f90f630094c6ec81227b554904
However note that it’s a 2.2 GiB file. I think it’s OK for hydra to
serve it, in particular because ‘guix publish’ does almost no processing
on that file since it’s already compressed. So the only cost is
bandwidth.
(The ‘texlive-texmf’ binary remains unavailable on hydra because it’s
marked as non-substitutable.)
Other options that came to mind were:
1. Mark the texlive-texmf source derivation as non-substitutable,
which would have required fiddling with ‘url-fetch’ to pass
#:substitutable? #f to ‘raw-derivation’. Everyone would have
downloaded from the upstream FTP site.
2. Add a ‘--hide=.*texlive-texmf*’ option to ‘guix publish’, which
would prevent it from publishing narinfos for store items that
match the regexp.
Ludo’.
next prev parent reply other threads:[~2018-01-19 13:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-18 12:52 bug#30157: texlive-20170524-texmf.tar.xz' failed: 410, "Gone" Mathieu Lirzin
2018-01-18 13:56 ` ng0
2018-01-18 13:17 ` Mathieu Lirzin
2018-01-18 15:07 ` ng0
2018-01-19 13:22 ` Ludovic Courtès [this message]
2018-01-19 14:51 ` Mathieu Lirzin
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=87lggu56g5.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=30157-done@debbugs.gnu.org \
--cc=mthl@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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).