-
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
cargo new
creates a weird _git2 symlink
#7173
Comments
Hm so I've actually been seeing this for quite some time as well but I figured it was some local issue I hadn't figured out yet. I'm in basically the same situation, and this affects the beta channel as well. I suspect this is tied to the recent update to libgit2, but for some reason this isn't happening on our CI because it causes issues with tests as well... @ehuss do you know if this is perhaps a bug that was fixed recently in libgit2? |
Oh nvmd, I also possess the power of searching the internet. Looks like this was a bug in libgit2 (libgit2/libgit2#5147) fixed in libgit2/libgit2#5151 |
Primarily pull in libgit2/libgit2#5151 to help address rust-lang/cargo#7173
Bring in a few updates, used to update libgit2 and fix a Windows issue as well as updating the `url` dependencies. Closes rust-lang#7173
Tighten requirements for git2 crates Bring in a few updates, used to update libgit2 and fix a Windows issue as well as updating the `url` dependencies. Closes #7173
I am still seeing this behavior in version 1.37. I installed rustup-init.exe from the main rust-lang.org site this evening and ran |
@azureskydiver We did not backport the fix to 1.37. Honestly, I didn't think about it, and didn't really expect many people to enable |
Problem
I'm not sure if it's even a bug, but I am running on Windows 10 Pro. I use Git Bash, as my "terminal", and when I create a new rust binary project, along with all the expected files/directories, I get what looks like a weird link file to some sort of
testing
file/dir.If I try to open that link as a directory, I get an error that it doesn't exist. Is this some temporary working directory that is not being cleaned up?
Steps
With the below versions of cargo/git, issue the following commands:
cargo new foo
.cd foo
ls -l
Notes
Here's the relevant transcript of commands indicating what I see, and the versions of relevant tools:
The text was updated successfully, but these errors were encountered: