-
Notifications
You must be signed in to change notification settings - Fork 2.7k
Closed
Labels
A-gitArea: anything dealing with gitArea: anything dealing with gitA-testing-cargo-itselfArea: cargo's testsArea: cargo's testsC-feature-requestCategory: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted`Category: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted`Command-publishS-acceptedStatus: Issue or feature is accepted, and has a team member available to help mentor or reviewStatus: Issue or feature is accepted, and has a team member available to help mentor or review
Description
It seems that cargo works fine if a worktree hasn't been changed around much, since testing with a brand new worktree worked fine. However, these steps cause problems:
git checkout -b cargo-worktree
git worktree add ../foo-worktree cargo-worktree
cd ../
mv foo-worktree foo-cargo-worktree
cd foo-cargo-worktree
cargo pacakge -l
As for why you'd possibly do this: I have a worktree to track the 'previous version branch' of hyper. It started as a worktree of 0.8.x, and eventually its become 0.10.x, and I updated the name of the directory. All git commands work fine, but I cannot cargo publish.
This works fine with cargo 0.18.0 (fe7b0cdcf 2017-04-24), but fails with cargo 0.20.0-nightly (38ca9b702 2017-05-14).
Metadata
Metadata
Assignees
Labels
A-gitArea: anything dealing with gitArea: anything dealing with gitA-testing-cargo-itselfArea: cargo's testsArea: cargo's testsC-feature-requestCategory: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted`Category: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted`Command-publishS-acceptedStatus: Issue or feature is accepted, and has a team member available to help mentor or reviewStatus: Issue or feature is accepted, and has a team member available to help mentor or review