Installed git hash doesn't match latest even when they should.

[svmnotn]

I have installed i3status-rust from its git repo, and it hasn't had a commit in 4 days, but when I run cargo install-update -ag it tries to update it due to it listing a different hash. This has happened with other packages install through git

[svmnotn]

I suppose this should be fixed when this cargo issue is resolved

[svmnotn]

If we run cargo uninstall followed by an install from the git repo the issue is solved. This is how I've been temporarily fixing it, thus only using cargo update to tell me the version changed.
As in:

1. Running cargo install-update, says there is an update to a git package.
2. Optionally cancel that update as that will save time.
3. Run cargo uninstall $packge
4. Run cargo install --git $repo
5. Re run cargo install-update if you have more git packges to check.

[matthiaskrgr]

Is there a way to

1. check if the package needs update, if yes
2. do a release build, if release build succeeds
3. cargo uninstall the old version
4. reinstall the new version (without having to rebuild)
   ?

IMO just uninstalling first and then trying to build the latest version is bad because if build fails, we end up with no running version on the system.

[svmnotn]

1. yes, that is what install-update does to decide whether to do something or not.
2. should be as simple as doing what they already do
3. this would depend on install-update keeping track on whether the build went ok or not, but should be doable?
4. just redo step 2, I guess.
   The issue is that this means git packages that need an update are compiled twice.

[mati865]

The fix has made it through and is available from rustc 1.28.0-nightly (5bf68db6e 2018-05-28) onwards.

[nabijaczleweli]

Nice! Will close when fix hits stable.

[mati865]

Rust 1.28 is stable already.

[nabijaczleweli]

Thanks for watching out!