From: Jack Hill <jackhill@jackhill.us>
To: zimoun <zimon.toutoune@gmail.com>
Cc: 47474@debbugs.gnu.org, phodina <phodina@protonmail.com>
Subject: bug#47474: fossil: hash mismatch
Date: Tue, 5 Jul 2022 10:55:03 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.21.2207051047260.32117@marsh.hcoop.net> (raw)
In-Reply-To: <86tugmsy7v.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1425 bytes --]
On Mon, 8 Nov 2021, zimoun wrote:
> Indeed, when looking forward. :-)
>
> However, in the context of Disarchive and long-term, it is seems
> relevant to keep it still open; as example to test “guix time-machine”
> and various fallbacks, IMHO.
I'm also curious to know to fill in the archive for old versions. I guess
the first step would be to preserve the tarballs with the original hashes.
Does anyone have them? I notice that this happened again with 2.17:
downloading from https://www.fossil-scm.org/home/tarball/f48180f2ff3169651a725396d4f7d667c99a92873b9c3df7eee2f144be7a0721/fossil-src-2.17.tar.gz ...
fossil-src-2.17.tar.gz 6.0MiB 4.0MiB/s 00:02 [##################] 100.0%
sha256 hash mismatch for /gnu/store/i695w5hp8vkgvkx40rs8p647mas0ldah-fossil-src-2.17.tar.gz:
expected hash: 1gvx6xzrw1a8snlq9qmr6099r44ifghg0h0fw4jazqmmyxriqzsw
actual hash: 18q5rc1d9d2zvrvsas5h419dv525ig9lyqswrx7bcl38zbjxics4
Looking forward:
I have asked upstream how we might avoid this problem:
https://fossil-scm.org/forum/forumpost/4903c3fcc1
We'll see what they say.
Some other ideas in the meantime:
1) Develop a fossil-fetch that can be used like git-fetch to download from
the source code repository directly.
2) Use git-fetch with the git-mirror. This would allow us to make use of
our current git integration with Software Heritage.
Best,
Jack
next prev parent reply other threads:[~2022-07-05 14:56 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 [this message]
2022-07-05 15:27 ` Ludovic Courtès
2022-07-05 15:45 ` Jack Hill
2022-07-05 15:49 ` Ludovic Courtès
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
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=alpine.DEB.2.21.2207051047260.32117@marsh.hcoop.net \
--to=jackhill@jackhill.us \
--cc=47474@debbugs.gnu.org \
--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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).