Skip to content
This repository has been archived by the owner on Oct 18, 2021. It is now read-only.

[email protected] was yanked #220

Closed
mmun opened this issue Jun 22, 2017 · 10 comments
Closed

[email protected] was yanked #220

mmun opened this issue Jun 22, 2017 · 10 comments

Comments

@mmun
Copy link

mmun commented Jun 22, 2017

Getting errors when I build:

error: no matching version `^0.3.1` found for package `chrono` (required by `mongodb`)
location searched: registry https://github.com/rust-lang/crates.io-index
versions found: 0.4.0, 0.3.0, 0.2.25, ...

More details chronotope/chrono#156

@pengshaomin
Copy link

me to

@jjpe
Copy link

jjpe commented Jun 22, 2017

This just hit me as well. A new mongodb release that relies on chrono 0.4.0 instead would be most welcome.

@mmun
Copy link
Author

mmun commented Jun 22, 2017

If we want to upgrade it looks like we'll need to wait until bson upgrades to [email protected] since this crate interfaces closely with bson. I have a patch ready for both crates.

@jjpe
Copy link

jjpe commented Jun 22, 2017

Any idea yet when those releases will take place?

@mmun
Copy link
Author

mmun commented Jun 22, 2017

Not sure but I'll submit a PR to bson-rs asap :)

@mmun
Copy link
Author

mmun commented Jun 22, 2017

mongodb/bson-rust#77

The other option, if bson-rs doesn't upgrade, is to downgrade the deps here to [email protected].

@jjpe
Copy link

jjpe commented Jun 22, 2017

Well I was just about to upgrade the dependencies actually, and being able to finish that properly would be nice.
But indeed, if really necessary I could just toss the changes, no harm done.

@saghm
Copy link
Contributor

saghm commented Jun 22, 2017

Thanks for reporting! @kyeah, any chance you could merge the fix for bson once you're not busy?

@kyeah
Copy link
Contributor

kyeah commented Jun 23, 2017

bson should be released on 0.9.0 — good to open a patch, @mmun (or @jjpe).

@saghm
Copy link
Contributor

saghm commented Jun 23, 2017

Fixed in #222 and published in 0.3.1. Thanks to everyone for notifying us about this issue!

@saghm saghm closed this as completed Jun 23, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants