Skip to content
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

Chrono dependency in Moment module causing conflicts #211

Open
ryanhossain9797 opened this issue May 23, 2020 · 2 comments
Open

Chrono dependency in Moment module causing conflicts #211

ryanhossain9797 opened this issue May 23, 2020 · 2 comments

Comments

@ryanhossain9797
Copy link

Cargo.toml in moment module has
[dependencies] chrono = "=0.4.8"
It causes conflicts with others using 0.4.11
such as

error: failed to select a version for chrono.
... required by package rustling-ontology-moment v0.19.3 (https://github.com/snipsco/rustling-ontology?tag=0.19.3#3bb1313d)
... which is depended on by rustling-ontology v0.19.3 (https://github.com/snipsco/rustling-ontology?tag=0.19.3#3bb1313d)
... which is depended on by snips-nlu-parsers v0.4.3 (https://github.com/snipsco/snips-nlu-parsers?tag=0.4.3#8cfdae50)
... which is depended on by snips-nlu-lib v0.65.6 (https://github.com/snipsco/snips-nlu-rs#88a047aa)
... which is depended on by terminal_alpha_beta v0.1.0 (/home/zireael9797/Storage/WebDev/rust/terminal_alpha_beta)
versions that meet the requirements = 0.4.8 are: 0.4.8

all possible versions conflict with previously selected packages.

previously selected package chrono v0.4.11
... which is depended on by discord v0.8.0 (https://github.com/SpaceManiac/discord-rs#767a930b)
... which is depended on by terminal_alpha_beta v0.1.0 (/home/zireael9797/Storage/WebDev/rust/terminal_alpha_beta)

failed to select a version for chrono which could resolve this conflict

@misha-krainik
Copy link

Hello. Is there any update or any solution to this problem you were experiencing @ryanhossain9797 ?

@ryanhossain9797
Copy link
Author

Hello. Is there any update or any solution to this problem you were experiencing @ryanhossain9797 ?

No, I eventually didn't need to deal with this issue any more since I stopped using the crate this has a conflict with.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants