search

prasad-kumkar / pallet-identity

Identity Pallet using Frame v1
The Unlicense
0 stars 1 forks source link

Troubles in adding pallet to substrate template #1

Open marcocomo opened 2 years ago

marcocomo commented 2 years ago

Hi! I'm trying to get the substrate-node-template working with the pallet you showed here, without any success... When it gets to compiling it this is what I get:

Updating git repository `https://github.com/prasad-kumkar/pallet-identity.git`
Updating crates.io index
error: failed to select a version for `parity-util-mem`.
... required by package `sp-core v3.0.0`
... which satisfies dependency `sp-core = "^3.0.0"` of package `frame-metadata v13.0.0`
... which satisfies dependency `frame-metadata = "^13.0.0"` of package `frame-support v3.0.0`
... which satisfies dependency `frame-support = "^3.0.0"` of package `frame-system v3.0.0`
... which satisfies dependency `frame-system = "^3.0.0"` of package `pallet-identity v3.0.0 (https://github.com/prasad-kumkar/pallet-identity.git#095a4869)`
... which satisfies git dependency `pallet-identity` of package `node-template-runtime v4.0.0-dev (/home/marcoc/thesis/greenchain/runtime)`
... which satisfies path dependency `node-template-runtime` (locked to 4.0.0-dev) of package `node-template v4.0.0-dev (/home/marcoc/thesis/greenchain/node)`
versions that meet the requirements `^0.9.0` are: 0.9.0

the package `parity-util-mem` links to the native library `parity-util-mem-ban-duplicates`, but it conflicts with a previous package which links to `parity-util-mem-ban-duplicates` as well:
package `parity-util-mem v0.10.2`
... which satisfies dependency `parity-util-mem = "^0.10"` (locked to 0.10.2) of package `kvdb v0.10.0`
... which satisfies dependency `kvdb = "^0.10"` (locked to 0.10.0) of package `kvdb-memorydb v0.10.0`
... which satisfies dependency `kvdb-memorydb = "^0.10.0"` (locked to 0.10.0) of package `sc-client-db v0.10.0-dev (https://github.com/paritytech/substrate.git?tag=monthly-2021-12#b6c1c1bc)`
... which satisfies git dependency `sc-client-db` (locked to 0.10.0-dev) of package `frame-benchmarking-cli v4.0.0-dev (https://github.com/paritytech/substrate.git?tag=monthly-2021-12#b6c1c1bc)`
... which satisfies git dependency `frame-benchmarking-cli` (locked to 4.0.0-dev) of package `node-template v4.0.0-dev (/home/marcoc/thesis/greenchain/node)`
Only one package in the dependency graph may specify the same links value. This helps ensure that only one copy of a native library is linked in the final binary. Try to adjust your dependencies so that only one package uses the links ='parity-util-mem' value. For more information, see https://doc.rust-lang.org/cargo/reference/resolver.html#links.

failed to select a version for `parity-util-mem` which could resolve this conflict

Dit it happen to you too when doing it?

Srinivas766 commented 2 years ago

yes