Closed str4d closed 1 month ago
As a temporary workaround, cargo install --locked cargo-dl
will install with the Cargo.lock
that was present at the time the latest cargo-dl
version was published, i.e. with an older crates-index
.
Fun, this is not the first time a dependency did a breaking http
update https://github.com/algesten/ureq/issues/683. I'll wait and see what happens to avoid any breakage from fixes.
I'm disappointed I didn't catch this earlier with my nightly CI job as it got auto-disabled. I'll have to work out some way to ensure all my repos nightly jobs remain running even when they don't need continuous maintenance :thinking:.
Looks like it's been fixed upstream now. Thanks for letting me know and opening the upstream issue!
cargo install cargo-dl
currently fails due tocargo-dl
usinghttp 0.2
, butcrates-index
migrating tohttp 1
(a breaking change under SemVer) in a non-breaking SemVer release. See https://github.com/frewsxcv/rust-crates-index/issues/172 for details.Possible solutions:
crates-index
to fix its SemVer violation, and then either do nothing (stay onhttp 0.2
), or migrate tohttp 1
andcrates-index 3
.http 1
andcrates-index >= 2.10
. This however runs a risk thatcrates-index
decides to fix its SemVer violation, which would breakcargo-dl
again.