Checksum errors with Rust 1.64.0 and 1.65.0

Checksum errors with Rust 1.64.0 and 1.65.0

[Matthew James Kraai]

[-- 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)))

Re: Checksum errors with Rust 1.64.0 and 1.65.0

[Efraim Flashner]

[-- 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 --]