unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Giovanni Biscuolo <g@xelera.eu>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: hash mismatch on permanently moved URL
Date: Thu, 2 Jul 2020 16:05:56 +0200	[thread overview]
Message-ID: <CAJ3okZ3ndOrv_HtDs+dPLv_fCF=xUv8XYa=E3k4gzRCk_3Ry0w@mail.gmail.com> (raw)
In-Reply-To: <87pn9ekpfy.fsf@roquette.i-did-not-set--mail-host-address--so-tickle-me>

On Thu, 2 Jul 2020 at 15:38, Giovanni Biscuolo <g@xelera.eu> wrote:

> Actually this is a in-place *displacement* (with HTML) :-O

I do not know what is an "inplace displacement (with HTML)".

> Anyway: I guess there will be potentially other issues like this one in
> the future (permanent redirections to web pages instead of sources) and
> unfortunately (AFAIU) Guix will not be able to use alternative sources
> like Software Heritage: WDYT about considering 301 and 302 HTTP codes as
> "soft failures" and making Guix considering the alternative sources?

Redirection should not be an issue.  The important point is the
integrity of the data (the sha256 field).
And here, there is a mismatch:

expected hash: 0v0xsf14xwlj125y9fd8lrhsaych4d8liv8gr746zng6g225szb2
actual hash:   1qfbm2kh7hzd8752rky9dzis8qhgkhs6dkq71k8zar8y74nz7265
                     08m27r3wrlaxrzzgjqnqsbcz8hmll9sbd1z1wk3js9wr09q3l1q5

Well, even I am not sure if the tarball is stable and if the checksum
does not vary.  Anyway!

> Problems like this one are very bad for our time machine, I'm just
> thinking if Guix can do something to prevent them.

I agree.  But Guix cannot fix the world. :-)
What is currently done seems The Right Thing:

 1. fetch from the Guix farm
 2. try with the current upstream
2b. try a mirror if any
 3. fallback to SWH

You hit the problem because you turn off the fallback to the Guix farm,

BTW, the fallback to SWH is not ready yet for 2 main reasons:

 a) SWH has not yet ingested all the source tarballs in existence of
Guix; and it is not ready.  What is ready is to ingest the current
source tarballs but nothing has been done to feed with all the past
source tarballs.
 b) It is not clear how to fetch back the raw tarball from SWH since
they do not store the checksum but their own hash id (SWHID).  Some
discussion about correspondence and so on is happening right now. :-)

> and guix pull is going on now, building half of the world! :-)

Nice if it works for you! :-)

Cheers,
simon


  reply	other threads:[~2020-07-02 14:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-02 12:32 hash mismatch on permanently moved URL Giovanni Biscuolo
2020-07-02 12:56 ` Efraim Flashner
2020-07-02 13:04 ` zimoun
2020-07-02 13:37   ` Giovanni Biscuolo
2020-07-02 14:05     ` zimoun [this message]
2020-07-02 17:21       ` Giovanni Biscuolo
2020-07-02 13:06 ` Giovanni Biscuolo
2020-07-02 13:43   ` Tobias Geerinckx-Rice
2020-07-24 15:21 ` Ludovic Courtès

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='CAJ3okZ3ndOrv_HtDs+dPLv_fCF=xUv8XYa=E3k4gzRCk_3Ry0w@mail.gmail.com' \
    --to=zimon.toutoune@gmail.com \
    --cc=g@xelera.eu \
    --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).