Bug 220968 - lang/rust fails to build on CURRENT with checksum failures
Summary: lang/rust fails to build on CURRENT with checksum failures
Status: Closed DUPLICATE of bug 221088
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: amd64 Any
: --- Affects Some People
Assignee: Jean-Sébastien Pédron
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-07-24 14:12 UTC by Nathan Whitehorn
Modified: 2017-07-30 11:06 UTC (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Nathan Whitehorn freebsd_committer freebsd_triage 2017-07-24 14:12:17 UTC 
Trying to build Rust on 12-CURRENT fails with the following error during unpacking of the bootstrap toolchain as of revision FreeBSD 12.0-CURRENT #3 r321376:

  extracting cargo-0.18.0-x86_64-unknown-freebsd/cargo/etc/bash_completions.d
  extracting cargo-0.18.0-x86_64-unknown-freebsd/cargo/etc/bash_completions.d/cargo
error: the listed checksum of `/usr/ports/lang/rust/work/rustc-1.18.0-src/src/vendor/libc/src/unix/bsd/freebsdlike/freebsd/x86.rs` has changed:
expected: 54311d3ebf2bb091ab22361e377e6ef9224aec2ecfe459fbfcedde4932db9c58
actual:   add7b601b7e4f1c83d3b3c72ae46fd9d53cc48249c922abfc765432553f498f1

The file reported changes from build attempt to build attempt -- I have also gotten aarch64.rs and mod.rs with similar errors.
Comment 1 Bugzilla Automation freebsd_committer freebsd_triage 2017-07-24 14:12:17 UTC 
Maintainer informed via mail
Comment 2 Jean-Sébastien Pédron freebsd_committer freebsd_triage 2017-07-26 17:03:40 UTC 
Hi!

I'm working on an update to Rust 1.19.0. Once this is committed, could you please tell me if this issue is still relevant?

Thanks!
Comment 3 Ekaterina Vaartis 2017-07-30 10:35:24 UTC 
Can confirm that this is still relevant with 1.19 on amd64
Comment 4 Jean-Sébastien Pédron freebsd_committer freebsd_triage 2017-07-30 11:06:28 UTC 

*** This bug has been marked as a duplicate of bug 221088 ***