You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying create a discord bot that can explore and interact with the Solana chain. Each piece on their own works just fine (the discord bot and solana project that is), but when I try to put them together it's dependency errors that I believe to have tracked down to this package. The issue seems to be that curve25519-dalek has zeroize v1 set as its dependency version. The current latest is 1.8.1. I experimented with versions and it seems 1.6.0 is the minimum I would need to have compatibility project wide. I understand that the Solana project needs to update on their end as well considering the current version of dalek.
DISCLAIMER: I understand that it may not be as simple as updating zeroize version in the Cargo.toml and hope nothings breaks. Even still I figured I'd ask.
Attached below is a cargo build output.
warning: unused manifest key: patches
Updating crates.io index
error: failed to select a version for zeroize.
... required by package curve25519-dalek v3.2.1
... which satisfies dependency curve25519-dalek = "^3.2.1" of package solana-program v2.0.10
... which satisfies dependency solana-program = "=2.0.10" of package solana-sdk v2.0.10
... which satisfies dependency solana-sdk = "^2.0.10" of package wesex v0.0.1 (/home/ki/Documents/wesex)
versions that meet the requirements >=1, <1.4 are: 1.3.0, 1.2.0, 1.1.1, 1.1.0, 1.0.0
all possible versions conflict with previously selected packages.
previously selected package zeroize v1.6.0
... which satisfies dependency zeroize = "^1.6.0" of package rustls v0.22.0
... which satisfies dependency rustls = "^0.22.0" of package tokio-tungstenite v0.21.0
... which satisfies dependency tokio-tungstenite = "^0.21.0" of package serenity v0.12.2
... which satisfies dependency serenity = "^0.12.2" of package wesex v0.0.1 (/home/ki/Documents/wesex)
failed to select a version for zeroize which could resolve this conflict
The text was updated successfully, but these errors were encountered:
I'm trying create a discord bot that can explore and interact with the Solana chain. Each piece on their own works just fine (the discord bot and solana project that is), but when I try to put them together it's dependency errors that I believe to have tracked down to this package. The issue seems to be that curve25519-dalek has zeroize v1 set as its dependency version. The current latest is 1.8.1. I experimented with versions and it seems 1.6.0 is the minimum I would need to have compatibility project wide. I understand that the Solana project needs to update on their end as well considering the current version of dalek.
DISCLAIMER: I understand that it may not be as simple as updating zeroize version in the Cargo.toml and hope nothings breaks. Even still I figured I'd ask.
Attached below is a cargo build output.
warning: unused manifest key: patches
Updating crates.io index
error: failed to select a version for
zeroize
.... required by package
curve25519-dalek v3.2.1
... which satisfies dependency
curve25519-dalek = "^3.2.1"
of packagesolana-program v2.0.10
... which satisfies dependency
solana-program = "=2.0.10"
of packagesolana-sdk v2.0.10
... which satisfies dependency
solana-sdk = "^2.0.10"
of packagewesex v0.0.1 (/home/ki/Documents/wesex)
versions that meet the requirements
>=1, <1.4
are: 1.3.0, 1.2.0, 1.1.1, 1.1.0, 1.0.0all possible versions conflict with previously selected packages.
previously selected package
zeroize v1.6.0
... which satisfies dependency
zeroize = "^1.6.0"
of packagerustls v0.22.0
... which satisfies dependency
rustls = "^0.22.0"
of packagetokio-tungstenite v0.21.0
... which satisfies dependency
tokio-tungstenite = "^0.21.0"
of packageserenity v0.12.2
... which satisfies dependency
serenity = "^0.12.2"
of packagewesex v0.0.1 (/home/ki/Documents/wesex)
failed to select a version for
zeroize
which could resolve this conflictThe text was updated successfully, but these errors were encountered: