Closed heidezomp closed 5 years ago
Update: cargo-install-update started working correctly again today, even though the latest commit for the previously failing repository has remained the same:
heidezomp@raggel ~> cargo install-update --all --git
Updating registry 'https://github.com/rust-lang/crates.io-index'
Package Installed Latest Needs update
bindgen v0.48.1 v0.48.1 No
cargo-asm v0.1.16 v0.1.16 No
cargo-bloat v0.6.2 v0.6.2 No
cargo-tree v0.25.0 v0.25.0 No
cargo-update v1.7.0 v1.7.0 No
cargo-watch v7.2.0 v7.2.0 No
No packages need updating.
Package Installed Latest Needs update
cargo-outdated 899a3d4457d65ac93a8f557bb09f2475c7e4a942 899a3d4457d65ac93a8f557bb09f2475c7e4a942 No
No git packages need updating.
I'll close this ticket and reopen it if it ever reoccurs.
Probably related to #99.
As of today updating crates installed from a git repository started failing:
I run this command as part of my daily upgrade routine, and it has always worked fine before.
The failing repository is
cargo-outdated
, since that's the only git repository in my config:I've never dug into the way cargo handles git repositories before, but as far as I can tell the repository on my disk is fine:
This is using cargo-install-update 1.7.0 on Arch Linux.