-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Fix git2 safe-directory disable #11366
Conversation
r? @epage (rustbot has picked a reviewer for you, use r? to override) |
In the process of fixing this, I noticed several other problems with git2, with fixes posted at libgit2/libgit2#6427 and rust-lang/git2-rs#894. I don't think either of those are necessary for cargo, though. Nominating for beta since this is a stable regression in 1.65. I'm not sure if it will be important for a stable backport. This is only the first report I've seen in the week since it is released, but it may be good to keep an eye on more reports. |
@bors r+ |
Fix git2 safe-directory disable The call to `set_verify_owner_validation` was not getting called unless a network configuration was found. This means in the common case that `cargo new` will fail when there is a safe-directory error. This fixes the issue by making sure that `set_verify_owner_validation` is called before the early-exits in `init_git_transports`. Fixes #11365
💔 Test failed - checks-actions |
☀️ Test successful - checks-actions |
Fix git2 safe-directory disable The call to `set_verify_owner_validation` was not getting called unless a network configuration was found. This means in the common case that `cargo new` will fail when there is a safe-directory error. This fixes the issue by making sure that `set_verify_owner_validation` is called before the early-exits in `init_git_transports`. Fixes rust-lang#11365
[beta-1.66] Backport fix for git2 safe-directory disable This is a beta backport of #11366.
5 commits in a3dfea71ca0c888a88111086898aa833c291d497..16b097879b6f117c8ae698aab054c87f26ff325e 2022-11-11 03:50:47 +0000 to 2022-11-14 23:28:16 +0000 - improve error message for cargo add/remove (rust-lang/cargo#11375) - Bump crate versions of `cargo-util` and `crates-io` (rust-lang/cargo#11369) - doc(changelog): suggestions of cargo fix are nightly only (rust-lang/cargo#11373) - Add warning when PATH env separator is in project path (rust-lang/cargo#11318) - Fix git2 safe-directory disable (rust-lang/cargo#11366)
Update cargo 5 commits in a3dfea71ca0c888a88111086898aa833c291d497..16b097879b6f117c8ae698aab054c87f26ff325e 2022-11-11 03:50:47 +0000 to 2022-11-14 23:28:16 +0000 - improve error message for cargo add/remove (rust-lang/cargo#11375) - Bump crate versions of `cargo-util` and `crates-io` (rust-lang/cargo#11369) - doc(changelog): suggestions of cargo fix are nightly only (rust-lang/cargo#11373) - Add warning when PATH env separator is in project path (rust-lang/cargo#11318) - Fix git2 safe-directory disable (rust-lang/cargo#11366) r? `@ghost`
The call to
set_verify_owner_validation
was not getting called unless a network configuration was found. This means in the common case thatcargo new
will fail when there is a safe-directory error. This fixes the issue by making sure thatset_verify_owner_validation
is called before the early-exits ininit_git_transports
.Fixes #11365