unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Matthew James Kraai <kraai@ftbfs.org>
To: guix-devel@gnu.org
Subject: Checksum errors with Rust 1.64.0 and 1.65.0
Date: Tue, 15 Nov 2022 04:36:42 -0800	[thread overview]
Message-ID: <56c226bf-bdfc-e485-0f19-d5284180cc38@ftbfs.org> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 934 bytes --]

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?

Matt

[-- Attachment #1.2: Type: text/html, Size: 1137 bytes --]

[-- Attachment #2: patch --]
[-- Type: text/plain, Size: 1189 bytes --]

diff --git a/gnu/packages/rust.scm b/gnu/packages/rust.scm
index 0f8b8cc54e..c16d458c54 100644
--- a/gnu/packages/rust.scm
+++ b/gnu/packages/rust.scm
@@ -617,6 +617,14 @@ (define rust-1.63
    ;; error: unrecognized platform-specific intrinsic function: `simd_arith_offset`
    rust-1.62 "1.63.0" "1l4rrbzhxv88pnfq94nbyb9m6lfnjwixma3mwjkmvvs2aqlq158z"))
 
+(define rust-1.64
+  (rust-bootstrapped-package
+   rust-1.63 "1.64.0" "018j720b2n12slp4xk64jc6shkncd46d621qdyzh2a8s3r49zkdk"))
+
+(define rust-1.65
+  (rust-bootstrapped-package
+   rust-1.63 "1.65.0" "0f005kc0vl7qyy298f443i78ibz71hmmh820726bzskpyrkvna2q"))
+
 ;;; Note: Only the latest versions of Rust are supported and tested.  The
 ;;; intermediate rusts are built for bootstrapping purposes and should not
 ;;; be relied upon.  This is to ease maintenance and reduce the time
@@ -625,7 +633,7 @@ (define rust-1.63
 ;;; Here we take the latest included Rust, make it public, and re-enable tests
 ;;; and extra components such as rustfmt.
 (define-public rust
-  (let ((base-rust rust-1.63))
+  (let ((base-rust rust-1.65))
     (package
       (inherit base-rust)
       (outputs (cons "rustfmt" (package-outputs base-rust)))

             reply	other threads:[~2022-11-15 12:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-15 12:36 Matthew James Kraai [this message]
2022-11-16  9:22 ` Checksum errors with Rust 1.64.0 and 1.65.0 Efraim Flashner

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=56c226bf-bdfc-e485-0f19-d5284180cc38@ftbfs.org \
    --to=kraai@ftbfs.org \
    --cc=guix-devel@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).