Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

"error: binary xxx already exists in destination" should print the full destination path #9797

Closed
jonas-schievink opened this issue Aug 17, 2021 · 4 comments · Fixed by #9850
Closed

"error: binary xxx already exists in destination" should print the full destination path #9797

jonas-schievink opened this issue Aug 17, 2021 · 4 comments · Fixed by #9850
Assignees
@Rustin170506
Labels
A-diagnostics Area: Error and warning messages generated by Cargo itself. C-bug Category: bug Command-install E-easy Experience: Easy

Comments

@jonas-schievink
Copy link
Contributor

jonas-schievink commented Aug 17, 2021 •
edited by rustbot
Loading

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.
@jonas-schievink jonas-schievink added the C-bug Category: bug label Aug 17, 2021
@ehuss ehuss added A-diagnostics Area: Error and warning messages generated by Cargo itself. Command-install E-easy Experience: Easy labels Aug 17, 2021
@Rustin170506

This comment has been minimized.

Sign in to view
@Rustin170506 Rustin170506 removed their assignment Aug 26, 2021
@Rustin170506
Copy link
Member

@rustbot claim

@trkohler trkohler mentioned this issue Aug 27, 2021
Closed
@trkohler
Copy link

sorry, I just read that the claim means
I may close the PR if @hi-rustin already started working on it

@Rustin170506
Copy link
Member

sorry, I just read that the claim means
I may close the PR if @hi-rustin already started working on it

Yes, I've done some work on it, but haven't submitted it yet.

@Rustin170506 Rustin170506 mentioned this issue Aug 28, 2021
Merged
@bors bors closed this as completed in 18751dd Sep 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Rustin170506 Rustin170506

Labels
A-diagnostics Area: Error and warning messages generated by Cargo itself. C-bug Category: bug Command-install E-easy Experience: Easy
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

print the full destination path when no track duplicates Rustin170506/cargo
4 participants
@ehuss @jonas-schievink @Rustin170506 @trkohler