[joshleeb]

This PR updates dependency crates itertools to 0.7.0 and log to 0.4.

Ref. #1265

[sgrif]

It looks like you accidentally updated a lot more than just those two dependencies, which has caused test failures. Did you maybe run cargo update on accident?

[joshleeb]

Did you maybe run cargo update on accident?

@sgrif I didn't run cargo update. My method was to update the itertools entry in Cargo.toml directly and then run cargo build.

I suspect it is during the build the other versions in the lock file are being updated?

[sgrif]

You might just want to make sure you've rebased on the latest master, then.

[sgrif]

Scratch that, this isn't your fault. The author of ring has yanked all versions of their crate including the one that we depend on. Any attempts to change Cargo.toml in any way will now break our build. I'm looking into this now.

[sgrif]

Update: Any changes to Cargo.toml will need to update Cargo.lock by hand unless the version of ring we depend on is unyanked (opened briansmith/ring#774 to try and get clarification) or we go through and update all of our transitive dependencies that use ring to 0.14. This involves a lot of crates that aren't actively maintained so that would be a major undertaking

[sgrif]

This is blocked on #1607

[bors]

☔ The latest upstream changes (presumably #1609) made this pull request unmergeable. Please resolve the merge conflicts.

[carols10cents]

@bors r+

[bors]

📌 Commit a7cbb3d has been approved by carols10cents

[bors]

⌛ Testing commit a7cbb3d with merge e418a15...

[bors]

☀️ Test successful - checks-travis
Approved by: carols10cents
Pushing e418a15 to master...