From: Giovanni Biscuolo <g@xelera.eu>
To: zimoun <zimon.toutoune@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: hash mismatch on permanently moved URL
Date: Thu, 02 Jul 2020 19:21:16 +0200 [thread overview]
Message-ID: <87k0zllto3.fsf@roquette.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <CAJ3okZ3ndOrv_HtDs+dPLv_fCF=xUv8XYa=E3k4gzRCk_3Ry0w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1805 bytes --]
zimoun <zimon.toutoune@gmail.com> writes:
> 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)".
Just a nonsense of mine :-)
[...]
> Redirection should not be an issue. The important point is the
> integrity of the data (the sha256 field).
> And here, there is a mismatch
Yes I go it, the very unusual thing is that the (double) redirection is
pointing to a web page (AFAIU) and *not* to the tgz source file
[...]
>> 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. :-)
...unfortunately not: it can fix *almost* all that is software related
> 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,
Yes I see, and actually it's a very specific use case
> 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. :-)
I was not aware of this second point: thanks!
[...]
Happy hacking! Gio'
--
Giovanni Biscuolo
Xelera IT Infrastructures
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2020-07-02 17:22 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
2020-07-02 17:21 ` Giovanni Biscuolo [this message]
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=87k0zllto3.fsf@roquette.i-did-not-set--mail-host-address--so-tickle-me \
--to=g@xelera.eu \
--cc=help-guix@gnu.org \
--cc=zimon.toutoune@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).