-
Notifications
You must be signed in to change notification settings - Fork 160
Open
Labels
Description
cargo-edit version: 0.13.0
cargo version: 1.82.0
When running cargo upgrade --incompatible with https://github.com/NixOS/rfc39/tree/ab3b4ac953d011d2fae04c252718dc81727a5a5d (and the patch section removed from the Cargo.toml), the following error occurs:
Checking rfc39's dependencies
name old req compatible latest new req
==== ======= ========== ====== =======
futures 0.1.28 0.1.31 0.3.31 0.3.31
hubcaps 0.5.0 0.5.0 0.6.2 0.6.2
hyper 0.12.33 0.12.36 1.5.1 1.5.1
lazy_static 1.3.0 1.5.0 1.5.0 1.5.0
serde 1.0.98 1.0.215 1.0.215 1.0.215
serde_json 1.0.40 1.0.133 1.0.133 1.0.133
slog 2.5 2.7.0 2.7.0 2.7
sloggers 0.3.2 0.3.6 2.2.0 2.2.0
structopt 0.2.18 0.2.18 0.3.26 0.3.26
tokio 0.1.22 0.1.22 1.41.1 1.41.1
slog-scope 4.1.2 4.4.0 4.4.0 4.4.0
slog-stdlog 4.0.0 4.1.1 4.1.1 4.1.1
prometheus 0.7 0.7.0 0.13.4 0.13
Upgrading recursive dependencies
error: no matching package named `wasm-bindgen` found
location searched: registry `crates-io`
required by package `reqwest v0.10.10`
... which satisfies dependency `reqwest = "^0.10"` of package `hubcaps v0.6.2`
... which satisfies dependency `hubcaps = "^0.6.2"` of package `rfc39 v0.1.0 (/Users/winter/src/rfc39)`
As a reminder, you're using offline mode (--offline) which can sometimes cause surprising resolution failures, if this error is too confusing you may wish to retry without the offline flag.
Error: recursive dependency update failed
The Cargo.toml and Cargo.lock file are touched at this point, and a cargo update reports no errors.
Not entirely sure what's going on here, but figured I'd leave it here just in case this is an issue with cargo-edit.