all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludovic.courtes@inria.fr>
To: Jack Hill <jackhill@jackhill.us>
Cc: 47474@debbugs.gnu.org, phodina <phodina@protonmail.com>,
	zimoun <zimon.toutoune@gmail.com>
Subject: bug#47474: fossil: hash mismatch
Date: Tue, 05 Jul 2022 17:49:40 +0200	[thread overview]
Message-ID: <87a69n4l0r.fsf@inria.fr> (raw)
In-Reply-To: <alpine.DEB.2.21.2207051139290.32117@marsh.hcoop.net> (Jack Hill's message of "Tue, 5 Jul 2022 11:45:14 -0400 (EDT)")

Hi!

Jack Hill <jackhill@jackhill.us> skribis:

> I guess I ran into this because I was using `guix build` with
> `--no-substitutes`. Is it expected that we don't fallback to
> disarchive and Software Heritage in that case?

Yes, and that’s actually suboptimal:

  https://issues.guix.gnu.org/28659

> If so, I guess my problem was an operator error. Can we close this
> ticket then, or are we still missing the tarballs for the older
> releases?

We would need to check whether older releases are available.  Disarchive
is relatively recent so they’re likely to be missing there, but Timothy
Sample has a Disarchive database that goes several years back, unlike
disarchive.guix.gnu.org.  Worth checking!

Anyhow, I think this issue can be closed.

Ludo’.




  reply	other threads:[~2022-07-05 15:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-29 15:33 bug#47474: fossil: hash mismatch zimoun
2021-11-04 21:46 ` phodina via Bug reports for GNU Guix
2021-11-08 11:06   ` zimoun
2022-07-05 14:55     ` Jack Hill
2022-07-05 15:27       ` Ludovic Courtès
2022-07-05 15:45         ` Jack Hill
2022-07-05 15:49           ` Ludovic Courtès [this message]
2022-07-05 16:50             ` 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=87a69n4l0r.fsf@inria.fr \
    --to=ludovic.courtes@inria.fr \
    --cc=47474@debbugs.gnu.org \
    --cc=jackhill@jackhill.us \
    --cc=phodina@protonmail.com \
    --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.
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.