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.

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

[beta] 1.51 backports #9277

Merged
merged 2 commits into from
Mar 16, 2021
Merged

[beta] 1.51 backports #9277

merged 2 commits into from
Mar 16, 2021

Conversation

ehuss
Copy link
Contributor

@ehuss ehuss commented Mar 16, 2021

Backports of:

…excrichton

Fix doc duplicate removal of root units.

The doc collision removal code didn't consider the possibility that there was a collision with a root unit.  This caused problems in conjunction with rust-lang#9142 where cargo would panic because a root unit got removed from the graph because of a filename collision. The solution here is to avoid removing root units during the doc collision sweep.

This has a downside that this reintroduces a filename collision.

An alternate solution would be to make the set of root units mutable, and remove from that list, but I figured this is simpler and more conservative.

Fixes rust-lang#9274
Fix --feature pkg/feat for V1 resolver for non-member.

rust-lang#8997 had an unintended regression where `-p foo --feature foo/feat` syntax where `foo` is an **optional non-member** fails with an error that `foo` did not match any packages.  The issue is that the member/feature selection routine needed to slot this into the features for the package in the current working directory (it was incorrectly treating `foo` as a workspace member).

V2 outright does not allow specifying features for non-workspace members.

Fixes rust-lang#9265
@rust-highfive
Copy link

r? @Eh2406

(rust-highfive has picked a reviewer for you, use r? to override)

@rust-highfive
Copy link

⚠️ Warning ⚠️

  • Pull requests are usually filed against the master branch for this repo, but this one is against rust-1.51.0. Please double check that you specified the right target!

@rust-highfive rust-highfive added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Mar 16, 2021
@alexcrichton
Copy link
Member

@bors: r+

@bors
Copy link
Collaborator

bors commented Mar 16, 2021

📌 Commit 77a13c0 has been approved by alexcrichton

@bors bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Mar 16, 2021
@bors
Copy link
Collaborator

bors commented Mar 16, 2021

⌛ Testing commit 77a13c0 with merge 43b129a...

@bors
Copy link
Collaborator

bors commented Mar 16, 2021

☀️ Test successful - checks-actions
Approved by: alexcrichton
Pushing 43b129a to rust-1.51.0...

@bors bors merged commit 43b129a into rust-lang:rust-1.51.0 Mar 16, 2021
bors added a commit to rust-lang-ci/rust that referenced this pull request Mar 17, 2021
[beta] Update cargo

1 commits in 35a2a434d37e796e2f013f577b3c481f518afd97..43b129a20fbf1ede0df411396ccf0c024bf34134
2021-03-12 01:08:31 +0000 to 2021-03-16 22:05:51 +0000
- [beta] 1.51 backports (rust-lang/cargo#9277)
@ehuss ehuss added this to the 1.51.0 milestone Feb 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants