unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Distopico <distopico@riseup.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 66345@debbugs.gnu.org
Subject: bug#66345: Invalid hash for rust-trybuild@1.0.19
Date: Wed, 04 Oct 2023 22:58:15 -0500	[thread overview]
Message-ID: <87bkddvhvz.fsf@riseup.net> (raw)
In-Reply-To: <87r0ma9vmc.fsf@inria.fr>


On 2023-10-04, Ludovic Courtès <ludo@gnu.org> wrote:

> Hello,
>
> We’re getting this:
>
> --8<---------------cut here---------------start------------->8---
> $ guix build -S rust-trybuild@1.0.19 
> The following derivation will be built:
>   /gnu/store/jxgkdnfi81520hx65z4mknndsxb3ggfw-rust-trybuild-1.0.19.tar.gz.drv
> building /gnu/store/jxgkdnfi81520hx65z4mknndsxb3ggfw-rust-trybuild-1.0.19.tar.gz.drv...
>
> Starting download of /gnu/store/wlr6y6l6m7752591nfkiz3rnfly6hd9p-rust-trybuild-1.0.19.tar.gz
> From https://crates.io/api/v1/crates/trybuild/1.0.19/download...
> following redirection to `https://static.crates.io/crates/trybuild/trybuild-1.0.19.crate'...
> downloading from https://crates.io/api/v1/crates/trybuild/1.0.19/download ...
>  download  22KiB                                        5.3MiB/s 00:00 ▕██████████████████▏ 100.0%
> sha256 hash mismatch for /gnu/store/wlr6y6l6m7752591nfkiz3rnfly6hd9p-rust-trybuild-1.0.19.tar.gz:
>   expected hash: 0ab7ahdx563n6kbm14pm3qnxq4fp06pz42nh5ii4acvlzycnwdh4
>   actual hash:   17xpybcdx76dm54dk7jvr5aickc4ia66qf57bazg7myx8pf6yzcq
> hash mismatch for store item '/gnu/store/wlr6y6l6m7752591nfkiz3rnfly6hd9p-rust-trybuild-1.0.19.tar.gz'
> build of /gnu/store/jxgkdnfi81520hx65z4mknndsxb3ggfw-rust-trybuild-1.0.19.tar.gz.drv failed
> View build log at '/var/log/guix/drvs/jx/gkdnfi81520hx65z4mknndsxb3ggfw-rust-trybuild-1.0.19.tar.gz.drv.gz'.
> guix build: error: build of `/gnu/store/jxgkdnfi81520hx65z4mknndsxb3ggfw-rust-trybuild-1.0.19.tar.gz.drv' failed
> $ guix describe
> Generation 275  Oct 01 2023 23:38:21    (current)
>   guix b9fae14
>     repository URL: https://git.savannah.gnu.org/git/guix.git
>     branch: master
>     commit: b9fae146d6cc4a6968a8eb18beef29aa1414a31e
> --8<---------------cut here---------------end--------------->8---
>
> It looks like the hash never matched.  Distopico, do you happen to have
> a copy with hash 0ab7ahdx563n6kbm14pm3qnxq4fp06pz42nh5ii4acvlzycnwdh4 on
> your disk?  If so, could you check how it compares to the one currently
> upstream?
>
> If not, we’ll go ahead and update the hash.
>
> Thanks,
> Ludo’.

Hi Ludo, thank you for let me know this, Here the patch fixing it,
https://issues.guix.gnu.org/66356

Thanks.




  reply	other threads:[~2023-10-05  4:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-04 16:54 bug#66345: Invalid hash for rust-trybuild@1.0.19 Ludovic Courtès
2023-10-05  3:58 ` Distopico [this message]
2023-10-05  9:30   ` 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=87bkddvhvz.fsf@riseup.net \
    --to=distopico@riseup.net \
    --cc=66345@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 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).