From: Tobias Geerinckx-Rice <me@tobias.gr>
To: 36614-done@debbugs.gnu.org
Cc: Ivan Petkov <ivanppetkov@gmail.com>
Subject: bug#36614: rust@1.36's hash is incorrect.
Date: Fri, 12 Jul 2019 15:16:20 +0200 [thread overview]
Message-ID: <87pnmf2y1n.fsf@nckx> (raw)
In-Reply-To: <8736jby4go.fsf@gmx.com>
[-- Attachment #1: Type: text/plain, Size: 963 bytes --]
Pierre, Ivan,
Pierre Langlois wrote:
> From
> https://static.rust-lang.org/dist/rustc-1.36.0-src.tar.gz...
> downloading from
> https://static.rust-lang.org/dist/rustc-1.36.0-src.tar.gz...
> rustc-1.36.0-src.tar.gz 147.5MiB
> 1.6MiB/s 01:35 [##################] 100.0%
> sha256 hash mismatch for
> /gnu/store/jm9xvf6qy4zxkb7rkmpz8ygf55l8v8v5-rustc-1.36.0-src.tar.gz:
> expected hash:
> 18r688ih4xi9m8gv55g1amb8inrwkdxp5fbcqb6i4gqxi90l3i0m
> actual hash:
> 06xv2p6zq03lidr0yaf029ii8wnjjqa894nkmrm6s0rx47by9i04
I get that too.
> Hopefully it's not unstable :-/.
Since release archives are signed that would imply some horrible
things about their key management, so I doubt it very much. I
guess we'll find out.
I've gone ahead and pushed a fix since the signature checked out.
I'm closing this bug for now...
However, I'd be interested to know what the previous hash
described. Do you still have that file around, Ivan?
Thanks,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2019-07-12 13:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-12 9:41 bug#36614: rust@1.36's hash is incorrect Pierre Langlois
[not found] ` <handler.36614.B.156292453627169.ack@debbugs.gnu.org>
2019-07-12 13:11 ` bug#36614: Acknowledgement (rust@1.36's hash is incorrect.) Pierre Langlois
2019-07-12 13:16 ` Tobias Geerinckx-Rice [this message]
2019-07-12 16:33 ` bug#36614: rust@1.36's hash is incorrect Ivan Petkov
2019-07-12 17:23 ` Leo Famulari
2019-07-12 17:26 ` Tobias Geerinckx-Rice
2019-07-13 0:59 ` Ivan Petkov
2019-07-12 17:27 ` Tobias Geerinckx-Rice
2019-07-12 17:34 ` Tobias Geerinckx-Rice
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=87pnmf2y1n.fsf@nckx \
--to=me@tobias.gr \
--cc=36614-done@debbugs.gnu.org \
--cc=ivanppetkov@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).