It is sometimes not obvious if the cargo install destination path was changed by a stray configuration file (or one implicitly set up by CI), or by an environment variable, which can make this error somewhat hard to properly diagnose. It would be great if Cargo provided the full destination path as part of the error message so that the user knows where to look for conflicting files.