-
Notifications
You must be signed in to change notification settings - Fork 15
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
blake3 sdists 1.0.1 / 1.0.2 are not compatible with Rust < 1.78 (Cargo.lock v4) #56
Comments
@tiran could you open a PR? |
Already working on a PR and figuring out the lowest possible MSRV. 1.66 seems to do the trick:
|
Rust 1.83 bumped the `Cargo.lock` format to `v4`. Specify and test a lower MSRV to force `Cargo.lock` format `v3`. The oldest working rustc version is 1.66: ``` error: package `constant_time_eq v0.3.1` cannot be built because it requires rustc 1.66.0 or newer ``` Fixes: oconnor663#56 Signed-off-by: Christian Heimes <[email protected]>
Rust 1.66 is the oldest toolchain that can compile blake3 and its dependencies. Our build pipeline is currently on Rust 1.75. I chose the older version just in case somebody else needs to build with an even older toolchain. For comparison, latest PyCA cryptography release 44.0 has MSRV 1.65, https://github.com/pyca/cryptography/blob/44.0.0/Cargo.toml#L19 |
@ddelange I didn't bump the release version in my PR. You have tagged the last commit as |
damn, thanks for opening #58 |
The source distributions blake3-1.0.2.tar.gz and 1.0.1 contain a
Cargo.lock
file with new lock format v4. This makes the sdists incompatible with Rust < 1.78. The Rust code itself builds fine with toolchain 1.75 and maybe even older versions. The sdist blake3-1.0.0.tar.gz contains aCargo.lock
v3.I guess your build system creates the sdist with latest stable version of Rust toolchain.
Cargo.lock
v4 support was added in Rust 1.78 and became the default in 1.83. Could you please add an appropriate MSRV toCargo.toml
to generate a v3Cargo.lock
?From Cargo changelog:
See huggingface/hf_transfer#55 / huggingface/hf_transfer#58 for the same type of issue
The text was updated successfully, but these errors were encountered: