From: Efraim Flashner <efraim@flashner.co.il>
To: Matthew James Kraai <kraai@ftbfs.org>
Cc: guix-devel@gnu.org
Subject: Re: Checksum errors with Rust 1.64.0 and 1.65.0
Date: Wed, 16 Nov 2022 11:22:47 +0200 [thread overview]
Message-ID: <Y3Sr57XXjCH3SxVh@3900XT> (raw)
In-Reply-To: <56c226bf-bdfc-e485-0f19-d5284180cc38@ftbfs.org>
[-- Attachment #1: Type: text/plain, Size: 1525 bytes --]
On Tue, Nov 15, 2022 at 04:36:42AM -0800, Matthew James Kraai wrote:
> Hi,
>
> I'm trying to package Rust 1.65.0. When I try to build it, it fails with
> the following error:
>
> starting phase `build'
> Building rustbuild
> error: checksum for `windows_x86_64_msvc v0.36.1` changed between lock files
>
> this could be indicative of a few possible errors:
>
> * the lock file is corrupt
> * a replacement source in use (e.g., a mirror) returned a different checksum
> * the source itself may be corrupt in one way or another
>
> unable to verify that `windows_x86_64_msvc v0.36.1` is the same as when the lockfile was generated
>
> failed to run: /gnu/store/8l1m8hy3aifx8v8gmvndncld8ngyv6mm-rust-1.63.0-cargo/bin/cargo build --manifest-path /tmp/guix-build-rust-1.65.0.drv-0/rustc-1.65.0-src/src/bootstrap/Cargo.toml --frozen
>
> The name of the crate (i.e., windows_x86_64) changes across runs. The same
> error happens with Rust 1.64.0, but not any earlier versions. Does anyone
> know how to resolve this?
As I'm guessing you may have seen, we do now have rust-1.65 in guix. It
turns out that due to the way some sources seem to have changed with
1.64 we now need to adjust the checksums in src/bootstrap/Cargo.lock in
addition to the Cargo.lock ones.
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2022-11-16 9:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-15 12:36 Checksum errors with Rust 1.64.0 and 1.65.0 Matthew James Kraai
2022-11-16 9:22 ` Efraim Flashner [this message]
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=Y3Sr57XXjCH3SxVh@3900XT \
--to=efraim@flashner.co.il \
--cc=guix-devel@gnu.org \
--cc=kraai@ftbfs.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).