unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Brian Woodcox <bw@inskydata.com>
To: help-guix@gnu.org
Subject: Re: Where is the best place to download texlive-20170524-extra.tar.xz ?
Date: Sat, 3 Nov 2018 08:44:04 -0600	[thread overview]
Message-ID: <9B11A236-9FA4-40BC-95BA-65FE0C2106C2@inskydata.com> (raw)
In-Reply-To: <87d0rmadj2.fsf@netris.org>

Thanks Mark.

That makes sense.

So I will just use the --no-check-certificate flag since the hash is used for verification in the end anyway.

This is really a nice feature being able to download packages from untrusted sites.

> On Nov 3, 2018, at 12:19 AM, Mark H Weaver <mhw@netris.org> wrote:
> 
> Hi Brian,
> 
> When looking for a file that Guix is trying to download but which is no
> longer available at the expected URL, I normally just do a web search
> for the file name, in this case "texlive-20170524-extra.tar.xz".  Any
> site will do.  It needn't be a site you trust, because Guix always
> checks the sha256 hash anyway.
> 
> If you "guix download" a file with the right name but the wrong
> contents, it will be successfully added to the store, but with the wrong
> hash string in the file name in /gnu/store, so nothing will ever use it.
> When you attempt to restart the build that failed, it will again try to
> download it, because the file it needs is not in the store.  The bogus
> file will be deleted the next time to run "guix gc".
> 
> I did a web search for this file name, and found this:
> 
> ftp://tug.org/texlive/historic/2017/texlive-20170524-extra.tar.xz
> 
>      Mark

      reply	other threads:[~2018-11-03 14:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-03  5:19 Where is the best place to download texlive-20170524-extra.tar.xz ? Brian Woodcox
2018-11-03  5:31 ` Brian Woodcox
2018-11-03  6:19 ` Mark H Weaver
2018-11-03 14:44   ` Brian Woodcox [this message]

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=9B11A236-9FA4-40BC-95BA-65FE0C2106C2@inskydata.com \
    --to=bw@inskydata.com \
    --cc=help-guix@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.
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).