-
-
Notifications
You must be signed in to change notification settings - Fork 14.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Recompute all cargoSha256/cargoHash #121994
Comments
Couldn't we apply the patch from rust-lang/cargo#9131 to our cargo? |
Indeed. One of my machines is currently recomputing all the hashes. So hopefully I'll be able to do a PR later today. |
Rust 1.50.0 incorporated a Cargo change (rust-lang/cargo#8937) in which cargo vendor erroneously changed permissions of vendored crates. This was fixed in Rust 1.51.0 (rust-lang/cargo#9131). Unfortunately, this means that all cargoSha256/cargoHashes produced during the Rust 1.50.0 cycle are potentially broken. This change updates cargoSha256/cargoHash tree-wide. Fixes NixOS#121994.
Rust 1.50.0 incorporated a Cargo change (rust-lang/cargo#8937) in which cargo vendor erroneously changed permissions of vendored crates. This was fixed in Rust 1.51.0 (rust-lang/cargo#9131). Unfortunately, this means that all cargoSha256/cargoHashes produced during the Rust 1.50.0 cycle are potentially broken. This change updates cargoSha256/cargoHash tree-wide. Fixes #121994.
#122016 has been merged |
This issue has been mentioned on NixOS Discourse. There might be relevant details there: https://discourse.nixos.org/t/cargo-lock-considered-harmful/49047/3 |
Describe the bug
Rust 1.50.0 incorporated a Cargo change (rust-lang/cargo#8937) in which
cargo vendor
erroneously changed permissions of vendored crates. This was fixed in Rust 1.51.0 (rust-lang/cargo#9131). Unfortunately, this means that allcargoSha256
/cargoHash
es produced during the Rust 1.50.0 cycle are potentially broken.The long-term solution for this issue is that we should probably apply our own normalization for permissions (#121259). But first, we should check/update
cargoSha256
/cargoHash
tree-wide.The text was updated successfully, but these errors were encountered: