Out-of-date dependencies

[paulhauner]

Description

We currently have several out-of-date dependencies which cannot be updated for various reasons. Whilst there's no immediate cause for concern, it's ideal for us to unblock these updates. This issue tracks these blockers.

• db-key: cannot be upgraded since leveldb uses 0.0.5.
• ring: cannot update since it requires a version of cc that cannot be reconciled with the web3 crate
• web3: cannot update since the later versions removed support for IPC and it has yet to be reintroduced.
• enr: we maintain this crate and have chosen not to update it at this time.
• discv5: as above.

[blacktemplar]

Update:

Some out of date dependencies get updated here: #2032

A list of out of date dependencies that can't get updated currently:

Dependency	Blocking Reson
bytes 0.5.6→0.6.0	reqwest requires bytes ^0.5 (seanmonstar/reqwest#1076)
db-key 0.0.5→0.1.0	leveldb requires db-key ^0.0.5 (skade/leveldb#14)
flate2 1.0.14→1.0.19	zip requires flate2 <= 1.0.14 (https://github.com/zip-rs/zip/blob/f5061c25e92c8808f27afbc7ea42f0bdc563c9c4/Cargo.toml#L15)
tokio-util 0.4.0→0.5.0	requires bytes ^0.6 which conflicts with libp2ps requirement bytes ^0.5. Furthermore libp2p can't update to bytes ^0.6 because futures_codec requires bytes ^0.5 (matthunz/futures-codec#51)
unsigned-varint fork	tokio-util updated to 0.4.0 + other updates (needed for tokio 0.3) (paritytech/unsigned-varint#38)
libp2p fork	gossipsub implementation (libp2p/rust-libp2p#1720)
warp fork	update to tokio 0.3 (seanmonstar/warp#753, seanmonstar/warp#741)
milagro_bls fork	why not submit to crates.io @kirk-baird?

[kirk-baird]

That's a good question, I'm happy to have it on crates.io, what are your thoughts @paulhauner?

Also it is worth updating milagro_bls to v1.4.1 from v1.4.0 as it fixes naming issues for windows users. (i.e. removes :)

[blacktemplar]

I just saw that the web3 got updated in #1989, updated the table :)