cargo-update: Update fails when a package is installed from a custom registry
I have a binary which is installed from a custom registry. Now cargo install-update -l or cargo install-update -a fails with
Updating registry 'https://github.com/rust-lang/crates.io-index'
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: "package ... not found"', src/libcore/result.rs:1188:5
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Is there a way to search all configured registries or maybe even just skip the failed packages?
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 15 (7 by maintainers)
Commits related to this issue
- Handle non-crates.io-registry packages (hopefully) Ref: #128 — committed to nabijaczleweli/cargo-update by nabijaczleweli 4 years ago
- Hopefully match up our hash with Cargo's Ref: #128 — committed to nabijaczleweli/cargo-update by nabijaczleweli 4 years ago
- Rename CargoRepoPackage to RegistryPackage. Fix tests. Fix error reporting in get_index_path() Ref: #128 — committed to nabijaczleweli/cargo-update by nabijaczleweli 4 years ago
- Rename RegistryPackage::registry_url to registry. Implement an actually correct get_index_url() with tests Ref: #128 — committed to nabijaczleweli/cargo-update by nabijaczleweli 4 years ago
But it only works, when both entries are present 🤷‍♂️ Thank you for helping!
Oh neat, I didn’t actually know about those before! This might warrant an issue on cloudsmith’s side, too.
Glad I could help!
Released in
v3.0.0!Seems to work! Thank you for the very fast response and fix!
Can you test current
masterbranch with the referenced commit?It has an experimental implementation of generic registry handling, so it should work for your usecase – your package should update from the right registry automatically and you should be able to install it from there via
(registry_url):package_name.