Re: Checksum errors with Rust 1.64.0 and 1.65.0

[Efraim Flashner <efraim@flashner.co.il>]

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