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
When using your library in combination with other crates, like the zip crate for example, both depend on the time crate, but with different versions.
This creates a dependency conflict in my project:
error: failed to select a version for `time`.
... required by package `zip v2.0.0`
... which satisfies dependency `zip = "^2.0.0"` of package `raspirus v1.2.0 (C:\...\Raspirus\src-tauri)`
versions that meet the requirements `^0.3.36` are: 0.3.36
all possible versions conflict with previously selected packages.
previously selected package `time v0.3.31`
... which satisfies dependency `time = "=0.3.31"` of package `leptonic v0.5.0`
... which satisfies dependency `leptonic = "^0.5.0"` of package `raspirus-ui v0.1.0 (C:\...\Raspirus)`
failed to select a version for `time` which could resolve this conflict
You can reproduce this issue by modifying the tauri-template provided here and add the zip crate to the src-tauri module.
The issue is also documented on the cargo and a potential solution could be to use a tool like cargo-semver-check to find these issues before releasing the library.
The text was updated successfully, but these errors were encountered:
error: failed to select a version for `time`.
... required by package `leptonic v0.5.0`
... which satisfies dependency `leptonic = "^0.5"` of package `frontend v0.1.0 (/Users/daniel/git/fireside-chat/frontend)`
versions that meet the requirements `=0.3.31` are: 0.3.31
When using your library in combination with other crates, like the zip crate for example, both depend on the
time
crate, but with different versions.This creates a dependency conflict in my project:
You can reproduce this issue by modifying the tauri-template provided here and add the zip crate to the
src-tauri
module.The issue is also documented on the cargo and a potential solution could be to use a tool like cargo-semver-check to find these issues before releasing the library.
The text was updated successfully, but these errors were encountered: