-
Notifications
You must be signed in to change notification settings - Fork 2.6k
ARM64: cannot read/write system gitconfig #3071
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
Comments
This is intentional. The system config is located within |
Oh, and please note that it is not really intended for users to write stuff into the system config, that config really is "owned" by Git for Windows. Use |
That's my bad, sorry, but
maybe that's why I'm working with the binaries mentioned in #3053 (comment) by the way!
|
Got the issue with missing DLLs fixed by working with a more recent build, sorry for the confusion. The issue with the Git config is still present though. Please consider these differences: x64 Windows machine with 32-bit Git for Windows (used Windows Sandbox to ensure clean environment):
ARM64 Windows machine with ARM64 Git for Windows installed (build: https://github.com/dscho/git/actions/runs/597692856)
This leads to a plethora of problems, like:
So we need to change something in a way so that Git looks at |
That looks correct. If there is no
That does not look correct. I think this because the CMake-based build is missing this: Lines 436 to 440 in c177856
This will most likely have to be implemented in one form or another here: git/contrib/buildsystems/CMakeLists.txt Lines 207 to 208 in c177856
|
This commit moves the gitconfig on Windows to /etc/gitconfig, which is where Git expects it. For more details, see git-for-windows#3071 (comment) Signed-off-by: Dennis Ameling <[email protected]>
Alright, got that to work, curious to hear what you think of my approach: #3078 |
Currently, when Git for Windows is built with CMake, the system Git config is expected in a different location than when building via `make`: the former expects it to be in `<runtime-prefix>/mingw64/etc/gitconfig`, the latter in `<runtime-prefix>/etc/gitconfig`. Because of this, things like `git clone` do not work correctly (because cURL is no longer able to find its certificate bundle that it needs to validate HTTPS certificates). See the full bug report and discussion here: git-for-windows#3071 (comment). This commit aligns the CMake-based build by mimicking what is already done in `config.mak.uname`. This closes git-for-windows#3071. Signed-off-by: Dennis Ameling <[email protected]>
Currently, when Git for Windows is built with CMake, the system Git config is expected in a different location than when building via `make`: the former expects it to be in `<runtime-prefix>/mingw64/etc/gitconfig`, the latter in `<runtime-prefix>/etc/gitconfig`. Because of this, things like `git clone` do not work correctly (because cURL is no longer able to find its certificate bundle that it needs to validate HTTPS certificates). See the full bug report and discussion here: git-for-windows#3071 (comment). This commit aligns the CMake-based build by mimicking what is already done in `config.mak.uname`. This closes git-for-windows#3071. Signed-off-by: Dennis Ameling <[email protected]>
Currently, when Git for Windows is built with CMake, the system Git config is expected in a different location than when building via `make`: the former expects it to be in `<runtime-prefix>/mingw64/etc/gitconfig`, the latter in `<runtime-prefix>/etc/gitconfig`. Because of this, things like `git clone` do not work correctly (because cURL is no longer able to find its certificate bundle that it needs to validate HTTPS certificates). See the full bug report and discussion here: #3071 (comment). This commit aligns the CMake-based build by mimicking what is already done in `config.mak.uname`. This closes #3071. Signed-off-by: Dennis Ameling <[email protected]>
Currently, when Git for Windows is built with CMake, the system Git config is expected in a different location than when building via `make`: the former expects it to be in `<runtime-prefix>/mingw64/etc/gitconfig`, the latter in `<runtime-prefix>/etc/gitconfig`. Because of this, things like `git clone` do not work correctly (because cURL is no longer able to find its certificate bundle that it needs to validate HTTPS certificates). See the full bug report and discussion here: #3071 (comment). This commit aligns the CMake-based build by mimicking what is already done in `config.mak.uname`. This closes #3071. Signed-off-by: Dennis Ameling <[email protected]>
Currently, when Git for Windows is built with CMake, the system Git config is expected in a different location than when building via `make`: the former expects it to be in `<runtime-prefix>/mingw64/etc/gitconfig`, the latter in `<runtime-prefix>/etc/gitconfig`. Because of this, things like `git clone` do not work correctly (because cURL is no longer able to find its certificate bundle that it needs to validate HTTPS certificates). See the full bug report and discussion here: #3071 (comment). This commit aligns the CMake-based build by mimicking what is already done in `config.mak.uname`. This closes #3071. Signed-off-by: Dennis Ameling <[email protected]>
Currently, when Git for Windows is built with CMake, the system Git config is expected in a different location than when building via `make`: the former expects it to be in `<runtime-prefix>/mingw64/etc/gitconfig`, the latter in `<runtime-prefix>/etc/gitconfig`. Because of this, things like `git clone` do not work correctly (because cURL is no longer able to find its certificate bundle that it needs to validate HTTPS certificates). See the full bug report and discussion here: #3071 (comment). This commit aligns the CMake-based build by mimicking what is already done in `config.mak.uname`. This closes #3071. Signed-off-by: Dennis Ameling <[email protected]>
Currently, when Git for Windows is built with CMake, the system Git config is expected in a different location than when building via `make`: the former expects it to be in `<runtime-prefix>/mingw64/etc/gitconfig`, the latter in `<runtime-prefix>/etc/gitconfig`. Because of this, things like `git clone` do not work correctly (because cURL is no longer able to find its certificate bundle that it needs to validate HTTPS certificates). See the full bug report and discussion here: #3071 (comment). This commit aligns the CMake-based build by mimicking what is already done in `config.mak.uname`. This closes #3071. Signed-off-by: Dennis Ameling <[email protected]>
Currently, when Git for Windows is built with CMake, the system Git config is expected in a different location than when building via `make`: the former expects it to be in `<runtime-prefix>/mingw64/etc/gitconfig`, the latter in `<runtime-prefix>/etc/gitconfig`. Because of this, things like `git clone` do not work correctly (because cURL is no longer able to find its certificate bundle that it needs to validate HTTPS certificates). See the full bug report and discussion here: #3071 (comment). This commit aligns the CMake-based build by mimicking what is already done in `config.mak.uname`. This closes #3071. Signed-off-by: Dennis Ameling <[email protected]>
Currently, when Git for Windows is built with CMake, the system Git config is expected in a different location than when building via `make`: the former expects it to be in `<runtime-prefix>/mingw64/etc/gitconfig`, the latter in `<runtime-prefix>/etc/gitconfig`. Because of this, things like `git clone` do not work correctly (because cURL is no longer able to find its certificate bundle that it needs to validate HTTPS certificates). See the full bug report and discussion here: #3071 (comment). This commit aligns the CMake-based build by mimicking what is already done in `config.mak.uname`. This closes #3071. Signed-off-by: Dennis Ameling <[email protected]>
Currently, when Git for Windows is built with CMake, the system Git config is expected in a different location than when building via `make`: the former expects it to be in `<runtime-prefix>/mingw64/etc/gitconfig`, the latter in `<runtime-prefix>/etc/gitconfig`. Because of this, things like `git clone` do not work correctly (because cURL is no longer able to find its certificate bundle that it needs to validate HTTPS certificates). See the full bug report and discussion here: #3071 (comment). This commit aligns the CMake-based build by mimicking what is already done in `config.mak.uname`. This closes #3071. Signed-off-by: Dennis Ameling <[email protected]>
Currently, when Git for Windows is built with CMake, the system Git config is expected in a different location than when building via `make`: the former expects it to be in `<runtime-prefix>/mingw64/etc/gitconfig`, the latter in `<runtime-prefix>/etc/gitconfig`. Because of this, things like `git clone` do not work correctly (because cURL is no longer able to find its certificate bundle that it needs to validate HTTPS certificates). See the full bug report and discussion here: #3071 (comment). This commit aligns the CMake-based build by mimicking what is already done in `config.mak.uname`. This closes #3071. Signed-off-by: Dennis Ameling <[email protected]>
Currently, when Git for Windows is built with CMake, the system Git config is expected in a different location than when building via `make`: the former expects it to be in `<runtime-prefix>/mingw64/etc/gitconfig`, the latter in `<runtime-prefix>/etc/gitconfig`. Because of this, things like `git clone` do not work correctly (because cURL is no longer able to find its certificate bundle that it needs to validate HTTPS certificates). See the full bug report and discussion here: git-for-windows#3071 (comment). This commit aligns the CMake-based build by mimicking what is already done in `config.mak.uname`. This closes git-for-windows#3071. Signed-off-by: Dennis Ameling <[email protected]>
Currently, when Git for Windows is built with CMake, the system Git config is expected in a different location than when building via `make`: the former expects it to be in `<runtime-prefix>/mingw64/etc/gitconfig`, the latter in `<runtime-prefix>/etc/gitconfig`. Because of this, things like `git clone` do not work correctly (because cURL is no longer able to find its certificate bundle that it needs to validate HTTPS certificates). See the full bug report and discussion here: #3071 (comment). This commit aligns the CMake-based build by mimicking what is already done in `config.mak.uname`. This closes #3071. Signed-off-by: Dennis Ameling <[email protected]>
Currently, when Git for Windows is built with CMake, the system Git config is expected in a different location than when building via `make`: the former expects it to be in `<runtime-prefix>/mingw64/etc/gitconfig`, the latter in `<runtime-prefix>/etc/gitconfig`. Because of this, things like `git clone` do not work correctly (because cURL is no longer able to find its certificate bundle that it needs to validate HTTPS certificates). See the full bug report and discussion here: #3071 (comment). This commit aligns the CMake-based build by mimicking what is already done in `config.mak.uname`. This closes #3071. Signed-off-by: Dennis Ameling <[email protected]>
Currently, when Git for Windows is built with CMake, the system Git config is expected in a different location than when building via `make`: the former expects it to be in `<runtime-prefix>/mingw64/etc/gitconfig`, the latter in `<runtime-prefix>/etc/gitconfig`. Because of this, things like `git clone` do not work correctly (because cURL is no longer able to find its certificate bundle that it needs to validate HTTPS certificates). See the full bug report and discussion here: #3071 (comment). This commit aligns the CMake-based build by mimicking what is already done in `config.mak.uname`. This closes #3071. Signed-off-by: Dennis Ameling <[email protected]>
Currently, when Git for Windows is built with CMake, the system Git config is expected in a different location than when building via `make`: the former expects it to be in `<runtime-prefix>/mingw64/etc/gitconfig`, the latter in `<runtime-prefix>/etc/gitconfig`. Because of this, things like `git clone` do not work correctly (because cURL is no longer able to find its certificate bundle that it needs to validate HTTPS certificates). See the full bug report and discussion here: #3071 (comment). This commit aligns the CMake-based build by mimicking what is already done in `config.mak.uname`. This closes #3071. Signed-off-by: Dennis Ameling <[email protected]>
Currently, when Git for Windows is built with CMake, the system Git config is expected in a different location than when building via `make`: the former expects it to be in `<runtime-prefix>/mingw64/etc/gitconfig`, the latter in `<runtime-prefix>/etc/gitconfig`. Because of this, things like `git clone` do not work correctly (because cURL is no longer able to find its certificate bundle that it needs to validate HTTPS certificates). See the full bug report and discussion here: #3071 (comment). This commit aligns the CMake-based build by mimicking what is already done in `config.mak.uname`. This closes #3071. Signed-off-by: Dennis Ameling <[email protected]>
Currently, when Git for Windows is built with CMake, the system Git config is expected in a different location than when building via `make`: the former expects it to be in `<runtime-prefix>/mingw64/etc/gitconfig`, the latter in `<runtime-prefix>/etc/gitconfig`. Because of this, things like `git clone` do not work correctly (because cURL is no longer able to find its certificate bundle that it needs to validate HTTPS certificates). See the full bug report and discussion here: #3071 (comment). This commit aligns the CMake-based build by mimicking what is already done in `config.mak.uname`. This closes #3071. Signed-off-by: Dennis Ameling <[email protected]>
Currently, when Git for Windows is built with CMake, the system Git config is expected in a different location than when building via `make`: the former expects it to be in `<runtime-prefix>/mingw64/etc/gitconfig`, the latter in `<runtime-prefix>/etc/gitconfig`. Because of this, things like `git clone` do not work correctly (because cURL is no longer able to find its certificate bundle that it needs to validate HTTPS certificates). See the full bug report and discussion here: #3071 (comment). This commit aligns the CMake-based build by mimicking what is already done in `config.mak.uname`. This closes #3071. Signed-off-by: Dennis Ameling <[email protected]>
Currently, when Git for Windows is built with CMake, the system Git config is expected in a different location than when building via `make`: the former expects it to be in `<runtime-prefix>/mingw64/etc/gitconfig`, the latter in `<runtime-prefix>/etc/gitconfig`. Because of this, things like `git clone` do not work correctly (because cURL is no longer able to find its certificate bundle that it needs to validate HTTPS certificates). See the full bug report and discussion here: #3071 (comment). This commit aligns the CMake-based build by mimicking what is already done in `config.mak.uname`. This closes #3071. Signed-off-by: Dennis Ameling <[email protected]>
Currently, when Git for Windows is built with CMake, the system Git config is expected in a different location than when building via `make`: the former expects it to be in `<runtime-prefix>/mingw64/etc/gitconfig`, the latter in `<runtime-prefix>/etc/gitconfig`. Because of this, things like `git clone` do not work correctly (because cURL is no longer able to find its certificate bundle that it needs to validate HTTPS certificates). See the full bug report and discussion here: git-for-windows#3071 (comment). This commit aligns the CMake-based build by mimicking what is already done in `config.mak.uname`. This closes git-for-windows#3071. Signed-off-by: Dennis Ameling <[email protected]> Signed-off-by: Junio C Hamano <[email protected]>
Currently, when Git for Windows is built with CMake, the system Git config is expected in a different location than when building via `make`: the former expects it to be in `<runtime-prefix>/mingw64/etc/gitconfig`, the latter in `<runtime-prefix>/etc/gitconfig`. Because of this, things like `git clone` do not work correctly (because cURL is no longer able to find its certificate bundle that it needs to validate HTTPS certificates). See the full bug report and discussion here: #3071 (comment). This commit aligns the CMake-based build by mimicking what is already done in `config.mak.uname`. This closes #3071. Signed-off-by: Dennis Ameling <[email protected]>
Currently, when Git for Windows is built with CMake, the system Git config is expected in a different location than when building via `make`: the former expects it to be in `<runtime-prefix>/mingw64/etc/gitconfig`, the latter in `<runtime-prefix>/etc/gitconfig`. Because of this, things like `git clone` do not work correctly (because cURL is no longer able to find its certificate bundle that it needs to validate HTTPS certificates). See the full bug report and discussion here: #3071 (comment). This commit aligns the CMake-based build by mimicking what is already done in `config.mak.uname`. This closes #3071. Signed-off-by: Dennis Ameling <[email protected]>
Currently, when Git for Windows is built with CMake, the system Git config is expected in a different location than when building via `make`: the former expects it to be in `<runtime-prefix>/mingw64/etc/gitconfig`, the latter in `<runtime-prefix>/etc/gitconfig`. Because of this, things like `git clone` do not work correctly (because cURL is no longer able to find its certificate bundle that it needs to validate HTTPS certificates). See the full bug report and discussion here: #3071 (comment). This commit aligns the CMake-based build by mimicking what is already done in `config.mak.uname`. This closes #3071. Signed-off-by: Dennis Ameling <[email protected]>
Currently, when Git for Windows is built with CMake, the system Git config is expected in a different location than when building via `make`: the former expects it to be in `<runtime-prefix>/mingw64/etc/gitconfig`, the latter in `<runtime-prefix>/etc/gitconfig`. Because of this, things like `git clone` do not work correctly (because cURL is no longer able to find its certificate bundle that it needs to validate HTTPS certificates). See the full bug report and discussion here: #3071 (comment). This commit aligns the CMake-based build by mimicking what is already done in `config.mak.uname`. This closes #3071. Signed-off-by: Dennis Ameling <[email protected]>
Currently, when Git for Windows is built with CMake, the system Git config is expected in a different location than when building via `make`: the former expects it to be in `<runtime-prefix>/mingw64/etc/gitconfig`, the latter in `<runtime-prefix>/etc/gitconfig`. Because of this, things like `git clone` do not work correctly (because cURL is no longer able to find its certificate bundle that it needs to validate HTTPS certificates). See the full bug report and discussion here: #3071 (comment). This commit aligns the CMake-based build by mimicking what is already done in `config.mak.uname`. This closes #3071. Signed-off-by: Dennis Ameling <[email protected]>
Currently, when Git for Windows is built with CMake, the system Git config is expected in a different location than when building via `make`: the former expects it to be in `<runtime-prefix>/mingw64/etc/gitconfig`, the latter in `<runtime-prefix>/etc/gitconfig`. Because of this, things like `git clone` do not work correctly (because cURL is no longer able to find its certificate bundle that it needs to validate HTTPS certificates). See the full bug report and discussion here: #3071 (comment). This commit aligns the CMake-based build by mimicking what is already done in `config.mak.uname`. This closes #3071. Signed-off-by: Dennis Ameling <[email protected]>
Currently, when Git for Windows is built with CMake, the system Git config is expected in a different location than when building via `make`: the former expects it to be in `<runtime-prefix>/mingw64/etc/gitconfig`, the latter in `<runtime-prefix>/etc/gitconfig`. Because of this, things like `git clone` do not work correctly (because cURL is no longer able to find its certificate bundle that it needs to validate HTTPS certificates). See the full bug report and discussion here: #3071 (comment). This commit aligns the CMake-based build by mimicking what is already done in `config.mak.uname`. This closes #3071. Signed-off-by: Dennis Ameling <[email protected]>
Currently, when Git for Windows is built with CMake, the system Git config is expected in a different location than when building via `make`: the former expects it to be in `<runtime-prefix>/mingw64/etc/gitconfig`, the latter in `<runtime-prefix>/etc/gitconfig`. Because of this, things like `git clone` do not work correctly (because cURL is no longer able to find its certificate bundle that it needs to validate HTTPS certificates). See the full bug report and discussion here: #3071 (comment). This commit aligns the CMake-based build by mimicking what is already done in `config.mak.uname`. This closes #3071. Signed-off-by: Dennis Ameling <[email protected]>
Currently, when Git for Windows is built with CMake, the system Git config is expected in a different location than when building via `make`: the former expects it to be in `<runtime-prefix>/mingw64/etc/gitconfig`, the latter in `<runtime-prefix>/etc/gitconfig`. Because of this, things like `git clone` do not work correctly (because cURL is no longer able to find its certificate bundle that it needs to validate HTTPS certificates). See the full bug report and discussion here: #3071 (comment). This commit aligns the CMake-based build by mimicking what is already done in `config.mak.uname`. This closes #3071. Signed-off-by: Dennis Ameling <[email protected]>
Currently, when Git for Windows is built with CMake, the system Git config is expected in a different location than when building via `make`: the former expects it to be in `<runtime-prefix>/mingw64/etc/gitconfig`, the latter in `<runtime-prefix>/etc/gitconfig`. Because of this, things like `git clone` do not work correctly (because cURL is no longer able to find its certificate bundle that it needs to validate HTTPS certificates). See the full bug report and discussion here: #3071 (comment). This commit aligns the CMake-based build by mimicking what is already done in `config.mak.uname`. This closes #3071. Signed-off-by: Dennis Ameling <[email protected]>
Currently, when Git for Windows is built with CMake, the system Git config is expected in a different location than when building via `make`: the former expects it to be in `<runtime-prefix>/mingw64/etc/gitconfig`, the latter in `<runtime-prefix>/etc/gitconfig`. Because of this, things like `git clone` do not work correctly (because cURL is no longer able to find its certificate bundle that it needs to validate HTTPS certificates). See the full bug report and discussion here: #3071 (comment). This commit aligns the CMake-based build by mimicking what is already done in `config.mak.uname`. This closes #3071. Signed-off-by: Dennis Ameling <[email protected]>
Currently, when Git for Windows is built with CMake, the system Git config is expected in a different location than when building via `make`: the former expects it to be in `<runtime-prefix>/mingw64/etc/gitconfig`, the latter in `<runtime-prefix>/etc/gitconfig`. Because of this, things like `git clone` do not work correctly (because cURL is no longer able to find its certificate bundle that it needs to validate HTTPS certificates). See the full bug report and discussion here: #3071 (comment). This commit aligns the CMake-based build by mimicking what is already done in `config.mak.uname`. This closes #3071. Signed-off-by: Dennis Ameling <[email protected]>
Currently, when Git for Windows is built with CMake, the system Git config is expected in a different location than when building via `make`: the former expects it to be in `<runtime-prefix>/mingw64/etc/gitconfig`, the latter in `<runtime-prefix>/etc/gitconfig`. Because of this, things like `git clone` do not work correctly (because cURL is no longer able to find its certificate bundle that it needs to validate HTTPS certificates). See the full bug report and discussion here: #3071 (comment). This commit aligns the CMake-based build by mimicking what is already done in `config.mak.uname`. This closes #3071. Signed-off-by: Dennis Ameling <[email protected]>
Currently, when Git for Windows is built with CMake, the system Git config is expected in a different location than when building via `make`: the former expects it to be in `<runtime-prefix>/mingw64/etc/gitconfig`, the latter in `<runtime-prefix>/etc/gitconfig`. Because of this, things like `git clone` do not work correctly (because cURL is no longer able to find its certificate bundle that it needs to validate HTTPS certificates). See the full bug report and discussion here: #3071 (comment). This commit aligns the CMake-based build by mimicking what is already done in `config.mak.uname`. This closes #3071. Signed-off-by: Dennis Ameling <[email protected]>
Currently, when Git for Windows is built with CMake, the system Git config is expected in a different location than when building via `make`: the former expects it to be in `<runtime-prefix>/mingw64/etc/gitconfig`, the latter in `<runtime-prefix>/etc/gitconfig`. Because of this, things like `git clone` do not work correctly (because cURL is no longer able to find its certificate bundle that it needs to validate HTTPS certificates). See the full bug report and discussion here: #3071 (comment). This commit aligns the CMake-based build by mimicking what is already done in `config.mak.uname`. This closes #3071. Signed-off-by: Dennis Ameling <[email protected]>
Currently, when Git for Windows is built with CMake, the system Git config is expected in a different location than when building via `make`: the former expects it to be in `<runtime-prefix>/mingw64/etc/gitconfig`, the latter in `<runtime-prefix>/etc/gitconfig`. Because of this, things like `git clone` do not work correctly (because cURL is no longer able to find its certificate bundle that it needs to validate HTTPS certificates). See the full bug report and discussion here: #3071 (comment). This commit aligns the CMake-based build by mimicking what is already done in `config.mak.uname`. This closes #3071. Signed-off-by: Dennis Ameling <[email protected]>
Currently, when Git for Windows is built with CMake, the system Git config is expected in a different location than when building via `make`: the former expects it to be in `<runtime-prefix>/mingw64/etc/gitconfig`, the latter in `<runtime-prefix>/etc/gitconfig`. Because of this, things like `git clone` do not work correctly (because cURL is no longer able to find its certificate bundle that it needs to validate HTTPS certificates). See the full bug report and discussion here: #3071 (comment). This commit aligns the CMake-based build by mimicking what is already done in `config.mak.uname`. This closes #3071. Signed-off-by: Dennis Ameling <[email protected]>
Currently, when Git for Windows is built with CMake, the system Git config is expected in a different location than when building via `make`: the former expects it to be in `<runtime-prefix>/mingw64/etc/gitconfig`, the latter in `<runtime-prefix>/etc/gitconfig`. Because of this, things like `git clone` do not work correctly (because cURL is no longer able to find its certificate bundle that it needs to validate HTTPS certificates). See the full bug report and discussion here: #3071 (comment). This commit aligns the CMake-based build by mimicking what is already done in `config.mak.uname`. This closes #3071. Signed-off-by: Dennis Ameling <[email protected]>
Currently, when Git for Windows is built with CMake, the system Git config is expected in a different location than when building via `make`: the former expects it to be in `<runtime-prefix>/mingw64/etc/gitconfig`, the latter in `<runtime-prefix>/etc/gitconfig`. Because of this, things like `git clone` do not work correctly (because cURL is no longer able to find its certificate bundle that it needs to validate HTTPS certificates). See the full bug report and discussion here: #3071 (comment). This commit aligns the CMake-based build by mimicking what is already done in `config.mak.uname`. This closes #3071. Signed-off-by: Dennis Ameling <[email protected]>
Currently, when Git for Windows is built with CMake, the system Git config is expected in a different location than when building via `make`: the former expects it to be in `<runtime-prefix>/mingw64/etc/gitconfig`, the latter in `<runtime-prefix>/etc/gitconfig`. Because of this, things like `git clone` do not work correctly (because cURL is no longer able to find its certificate bundle that it needs to validate HTTPS certificates). See the full bug report and discussion here: #3071 (comment). This commit aligns the CMake-based build by mimicking what is already done in `config.mak.uname`. This closes #3071. Signed-off-by: Dennis Ameling <[email protected]>
Currently, when Git for Windows is built with CMake, the system Git config is expected in a different location than when building via `make`: the former expects it to be in `<runtime-prefix>/mingw64/etc/gitconfig`, the latter in `<runtime-prefix>/etc/gitconfig`. Because of this, things like `git clone` do not work correctly (because cURL is no longer able to find its certificate bundle that it needs to validate HTTPS certificates). See the full bug report and discussion here: #3071 (comment). This commit aligns the CMake-based build by mimicking what is already done in `config.mak.uname`. This closes #3071. Signed-off-by: Dennis Ameling <[email protected]>
Currently, when Git for Windows is built with CMake, the system Git config is expected in a different location than when building via `make`: the former expects it to be in `<runtime-prefix>/mingw64/etc/gitconfig`, the latter in `<runtime-prefix>/etc/gitconfig`. Because of this, things like `git clone` do not work correctly (because cURL is no longer able to find its certificate bundle that it needs to validate HTTPS certificates). See the full bug report and discussion here: #3071 (comment). This commit aligns the CMake-based build by mimicking what is already done in `config.mak.uname`. This closes #3071. Signed-off-by: Dennis Ameling <[email protected]>
Currently, when Git for Windows is built with CMake, the system Git config is expected in a different location than when building via `make`: the former expects it to be in `<runtime-prefix>/mingw64/etc/gitconfig`, the latter in `<runtime-prefix>/etc/gitconfig`. Because of this, things like `git clone` do not work correctly (because cURL is no longer able to find its certificate bundle that it needs to validate HTTPS certificates). See the full bug report and discussion here: #3071 (comment). This commit aligns the CMake-based build by mimicking what is already done in `config.mak.uname`. This closes #3071. Signed-off-by: Dennis Ameling <[email protected]>
Currently, when Git for Windows is built with CMake, the system Git config is expected in a different location than when building via `make`: the former expects it to be in `<runtime-prefix>/mingw64/etc/gitconfig`, the latter in `<runtime-prefix>/etc/gitconfig`. Because of this, things like `git clone` do not work correctly (because cURL is no longer able to find its certificate bundle that it needs to validate HTTPS certificates). See the full bug report and discussion here: #3071 (comment). This commit aligns the CMake-based build by mimicking what is already done in `config.mak.uname`. This closes #3071. Signed-off-by: Dennis Ameling <[email protected]>
Currently, when Git for Windows is built with CMake, the system Git config is expected in a different location than when building via `make`: the former expects it to be in `<runtime-prefix>/mingw64/etc/gitconfig`, the latter in `<runtime-prefix>/etc/gitconfig`. Because of this, things like `git clone` do not work correctly (because cURL is no longer able to find its certificate bundle that it needs to validate HTTPS certificates). See the full bug report and discussion here: #3071 (comment). This commit aligns the CMake-based build by mimicking what is already done in `config.mak.uname`. This closes #3071. Signed-off-by: Dennis Ameling <[email protected]>
Currently, when Git for Windows is built with CMake, the system Git config is expected in a different location than when building via `make`: the former expects it to be in `<runtime-prefix>/mingw64/etc/gitconfig`, the latter in `<runtime-prefix>/etc/gitconfig`. Because of this, things like `git clone` do not work correctly (because cURL is no longer able to find its certificate bundle that it needs to validate HTTPS certificates). See the full bug report and discussion here: #3071 (comment). This commit aligns the CMake-based build by mimicking what is already done in `config.mak.uname`. This closes #3071. Signed-off-by: Dennis Ameling <[email protected]>
This is not an urgent issue, since ARM64 Windows is only in the testing phase right now, and no official builds have been published yet.
Setup
ARM64 Windows test build: https://github.com/dscho/git/actions/runs/597692856
defaults?
to the issue you're seeing?
ARM64 😉
Details
Git Bash
Minimal, Complete, and Verifiable example
this will help us understand the issue.
git config --list
should show the Git configuration.git config --list
doesn't return anything. However, after I copied/etc/gitconfig
to/arm64/etc/gitconfig
,git config --list
started showing the correct output:... so the ARM64 Git for Windows (Bash at least) looks for
gitconfig
in the wrong folder.URL to that repository to help us with testing?
N/A
The text was updated successfully, but these errors were encountered: