Don't squash path dependencies with same package name #13863
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #13862
Dependencies with same package name in the
Cargo.lock
was squashed inEncodableResolve::into_resolve()
.e.g. In the problem reproduction repo's Cargo.lock, there are two entries:
However, they were squashed in
build_path_deps()
, then we endup getting two package ids with same path like this:This package version inconsistency triggers patch update introduced in #8248 everytime you compile this crate.