all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jan Nieuwenhuizen <janneke@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 28659@debbugs.gnu.org
Subject: bug#28659: v0.13: guix pull fails; libgit2-0.26.0 and 0.25.1 content hashes fail
Date: Mon, 02 Oct 2017 19:05:00 +0200	[thread overview]
Message-ID: <87infx8oqr.fsf@gnu.org> (raw)
In-Reply-To: <87o9ppoabw.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Mon, 02 Oct 2017 17:09:39 +0200")

Ludovic Courtès writes:

> What’s sad here is that we do have the right tarball at:
>
>   https://mirror.hydra.gnu.org/file/libgit2-0.25.1.tar.gz/sha256/1cdwcw38frc1wf28x5ppddazv9hywc718j92f3xa3ybzzycyds3s

Sad indeed!

> The problem is that the hash check is performed by guix-daemon itself,
> not by “guix perform-download”.  So when guix-daemon diagnoses a hash
> mismatch, it’s too late and we cannot try again and use the
> content-addressed mirror.

Why don't we try our content-addressed mirror first?

> A crude but helpful fix would be to have perform-download compute the
> hash by itself and act accordingly.  It’s crude because that means that
> we’d be computing the hash twice: once in ‘guix perform-download’ and a
> second time in guix-daemon.  For archives below ~20 MiB it’s probably OK
> though.
>
> Thoughts?

We may want more guix hackers' viewpoints here, I don't feel very
qualified...As this would be a temporary workaround only until we have

> In the future, with the daemon written in Guile, it’s one area where we
> could achieve better integration and coordination among the various
> pieces.

...it might be fine?

Do we want/need to bring out a new release for this, e.g. 0.13.1, or
even 0.14?  I'm not sure how bad it is that --no-substitutes does not
work.  I think working on guix pull to not compile everything locally
may have priority?

janneke

-- 
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com

  reply	other threads:[~2017-10-02 17:06 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-01 10:16 bug#28659: v0.13: guix pull fails; libgit2-0.26.0 and 0.25.1 content hashes fail Jan Nieuwenhuizen
2017-10-01 19:20 ` Jan Nieuwenhuizen
2017-10-01 20:42   ` Leo Famulari
2017-10-01 21:05     ` ng0
2017-10-02 14:57     ` Ludovic Courtès
2017-10-02 18:19       ` Leo Famulari
2017-10-02 22:47         ` Maxim Cournoyer
2017-10-03 12:31           ` Ludovic Courtès
2017-10-03 14:24           ` Leo Famulari
2017-10-04  4:22             ` Maxim Cournoyer
2017-10-04 16:54               ` Leo Famulari
2017-10-04 23:53                 ` Maxim Cournoyer
2017-10-05  4:52                   ` Maxim Cournoyer
2017-10-05  6:08                     ` Jan Nieuwenhuizen
2017-10-02 15:09 ` Ludovic Courtès
2017-10-02 17:05   ` Jan Nieuwenhuizen [this message]
2017-10-02 18:22   ` Leo Famulari
2017-10-02 20:00     ` Ludovic Courtès
2017-10-02 20:22       ` Jan Nieuwenhuizen
2017-10-02 20:29         ` Leo Famulari
2017-10-03 12:30         ` Ludovic Courtès
2017-10-20 21:17       ` Leo Famulari
2017-11-28 13:30         ` Ludovic Courtès
2017-12-14 16:53           ` Ludovic Courtès
2017-12-15  9:30             ` bug#28659: Always enable substitutes for fixed-output derivations Ludovic Courtès
2022-02-03  2:58               ` bug#28659: Content-addressed mirror is not used upon invalid hash zimoun

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87infx8oqr.fsf@gnu.org \
    --to=janneke@gnu.org \
    --cc=28659@debbugs.gnu.org \
    --cc=ludo@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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.