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

No longer installes, dependency version pin was yanked #433

Closed
dallinwright opened this issue Aug 25, 2021 · 3 comments
Closed

No longer installes, dependency version pin was yanked #433

dallinwright opened this issue Aug 25, 2021 · 3 comments

Comments

@dallinwright
Copy link

dallinwright commented Aug 25, 2021

The driver no longer downloads and compiles when added as a dependency starting today. A crate version that is pinned for hmac@0.7.1 is a very old version, which itself has a dependency to a crate that no longer exists. When adding to a project, this is the result.

Execution failed (exit code 101).
/home/dallin/.cargo/bin/cargo metadata --verbose --format-version 1 --all-features
stdout :     Updating crates.io index
error: failed to select a version for the requirement `crypto-mac = "^0.7"`
candidate versions found which didn't match: 0.11.1, 0.11.0, 0.10.1, ...
location searched: crates.io index
required by package `hmac v0.7.1`
    ... which is depended on by `mongodb v1.2.2`

Here is the screenshot of crypto-hmac@v0.7
image

I will add for whomever comes after me looking, switching to the latest beta release, for me mongodb = "2.0.0-beta.3", solves the issue as the versions are upgraded for these specific things.

@KernelErr
Copy link

KernelErr commented Aug 25, 2021

Meet the same problem. And seems that the 2.0.0 version is incompatible with the current 1.2.2 version, so some code has to be changed in order to pass compilation.

@mmecoco
Copy link

mmecoco commented Aug 25, 2021

Same problem here :(

@patrickfreed
Copy link
Contributor

Thank you for reporting this! We've just released v1.2.3 of the driver, which should fix this issue. As @KernelErr mentions, you can also updated to the latest 2.0 beta as well, though that will involve some breaking changes.

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

4 participants