cargo can't download futures-util-preview 0.3.0-alpha.4

[Arnavion]

Cargo.toml contains

[dependencies]
futures-util-preview = { version = "0.3.0-alpha.4", features = ["compat"] }

cargo update fails with:

error: no matching version `^0.3.0-alpha.4` found for package `futures-util-preview`
location searched: registry `https://github.com/rust-lang/crates.io-index`
versions found: 0.2.2

With RUST_LOG=debug :

INFO 2018-09-02T20:33:03Z: cargo::sources::registry::index: failed to parse `futures-util-preview` registry package: Feature `compat` includes `futures01` which is neither a dependency nor another feature

This is with latest nightly cargo cargo 1.29.0-nightly (0ec7281b9 2018-08-20). Seems it doesn't like the crate renaming feature.

[Nemo157]

Seems related to rust-lang/cargo#5753, probably the registry related code wasn’t changed to behave in the same way. Would be good to open a cargo issue about it.

[Arnavion]

Will do. Do you want to publish a new version without the crate renaming until then?

Edit: rust-lang/cargo#5962

[MajorBreakfast]

@Arnavion According to your post you're running an older nightly. alpha.4 requires at least 2018-08-31. Can you run rustup update and check whether the problem goes away?

Edit: Well you're right... doesn't work for me either

[Arnavion]

@MajorBreakfast As I said in OP, this is latest nightly cargo.

$ cargo -vV

cargo 1.29.0-nightly (0ec7281b9 2018-08-20)
release: 1.29.0
commit-hash: 0ec7281b9c36ca7f724bfac8b029633910270a48
commit-date: 2018-08-20


$ rustc -vV

rustc 1.30.0-nightly (28bcffead 2018-09-01)
binary: rustc
commit-hash: 28bcffead74d5e17c6cb1f7de432e37f93a6b50c
commit-date: 2018-09-01
host: x86_64-pc-windows-msvc
release: 1.30.0-nightly
LLVM version: 8.0

[MajorBreakfast]

@Arnavion I didn't know that cargo nightlies run on a different schedule. Now I do 🙂

[Nemo157]

The registry doesn’t contain any info on this renaming, so it seems likely that there will have to be a new version published with a new version of cargo to fix the registry issue. That will take some time to sort out, so I think it’d pay to revert the dependency renaming and publish alpha.5 now, we just miss out on being able to run the compat doctests so wont affect users at all.

[MajorBreakfast]

Alright, I'll release alpha.5 this evening. Earlier if there's a PR that updates the version numbers, the changelog and reverts our usage of cargo renaming. 😄

[MajorBreakfast]

Alpha 5 is released

[Arnavion]

Thanks. Confirmed it works.

[MajorBreakfast]

Perfect 👌