We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi
This line: https://github.com/paritytech/arkworks-substrate/blob/main/Cargo.toml#L32, because it does not specify any version/branch, fetches a lot of polkadot dependencies from master. This ends up mixing polkadot dependencies if you're tied to a specific polkadot version.
master
Depending on how a project orders the polkadot dependencies, it could lead to problems using two different crates at the same time.
The text was updated successfully, but these errors were encountered:
For anyone having this issue, you can add this to your Cargo.toml:
Cargo.toml
[patch."https://github.com/paritytech/polkadot-sdk"] sp-crypto-ec-utils = { git = "https://github.com/paritytech//polkadot-sdk", branch = "release-polkadot-v1.7.2" }
Note the double // in paritytech//polkadot-sdk is required to say cargo to treat the repo as a different one from the one in the patch url
//
paritytech//polkadot-sdk
patch
Sorry, something went wrong.
No branches or pull requests
Hi
This line: https://github.com/paritytech/arkworks-substrate/blob/main/Cargo.toml#L32, because it does not specify any version/branch, fetches a lot of polkadot dependencies from
master
. This ends up mixing polkadot dependencies if you're tied to a specific polkadot version.Depending on how a project orders the polkadot dependencies, it could lead to problems using two different crates at the same time.
The text was updated successfully, but these errors were encountered: