mingw64 Error for Git Installation about moonshine-sdk-installer HOT 10 OPEN

I found this command in Moonshine-IDE/Moonshine-IDE#739

%GIT_HOME%\bin\git config --global http.sslCAInfo %GIT_HOME%\mingw64\ssl\cert.pem

Are we still running this git config command on Windows?

from moonshine-sdk-installer.

Ah, @Aszusz found the original issue for this. Here the relevant writeup: Moonshine-IDE/Moonshine-IDE#487 (comment)

from moonshine-sdk-installer.

This wasted a lot of time for me again when testing today.

Testing with a fresh Windows VM, I installed Git and got this error:

I tried the previous fix and still got an error.

I found a slightly different solution here, and this worked for me.

# This path should be based on the path the MSDKI uses for GIT
set GIT_HOME=C:\MoonshineSDKs\Git\git-2.30.1
# This command uses the `.crt` instead of the `.pem`.  Also note that the directory is different 
%GIT_HOME%\bin\git config --global http.sslCAInfo %GIT_HOME%\mingw64\ssl\certs\ca-bundle.crt

from moonshine-sdk-installer.

I have updated the temp-environment-setup command to match this:

%GIT_HOME%\bin\git config --global http.sslCAInfo %GIT_HOME%\mingw64\ssl\certs\ca-bundle.crt

Please, check.

from moonshine-sdk-installer.

I didn't get any errors for the new install, but I had already set the global configuration. I'll retest this on a fresh Windows instance when I have a chance.

from moonshine-sdk-installer.

I did a test with MSDKI 4.5.0 build 414 (downloaded from the development builds on moonshine-ide.com) on a fresh Windows 11 machine, and I found that I still got the same error:

fatal: unable to access 'https://github.com/Moonshine-IDE/Moonshine-IDE/', error setting certificate verify locations:  CAfile: C:/Program Files/Git/mingw64/ssl/certis/ca-bundle.crt CApath: none

I checked the command line and confirmed that the global config values for http.sslCAInfo was not set.

from moonshine-sdk-installer.

So I rechecked the generated .cmd file that we use to set temporary environment on Windows, and I see the command generated in expected way:

set DYLD_LIBRARY_PATH=^C^:^\^M^o^o^n^s^h^i^n^e^S^D^K^s^\^H^a^x^e^\^n^e^k^o^-^2^.^3^.^0
set PATH=%FLEX_HOME%\bin;%AIR_SDK_HOME%\bin;%JAVA_HOME%\bin;%ANT_HOME%\bin;%MAVEN_HOME%\bin;%GRADLE_HOME%\bin;%GRAILS_HOME%\bin;%HAXE_HOME%;%NEKO_HOME%;%VIRTUALBOX_HOME%;%DYLD_LIBRARY_PATH%;%PATH%
"%GIT_HOME%\bin\git" config --global http.sslCAInfo "%GIT_HOME%\mingw64\ssl\certs\ca-bundle.crt"

When I ran the file on command-line manually, it didn't shown any warning/problem either. I wonder where it's breaking..

from moonshine-sdk-installer.

You can check the global config like this: "%GIT_HOME%\bin\git" config --global http.sslCAInfo. I confirmed this wasn't set after the installation.

I retested this today by:

1. Removing any existing global config value (i.e set manually) like this: "%GIT_HOME%\bin\git" config --global http.sslCAInfo ""
2. Delete or Rename C:\MoonshineSDKs\Git
3. Reinstall Git from MSDKI
4. Check the global config value with "%GIT_HOME%\bin\git" config --global http.sslCAInfo. BUG: it was not set. The log didn't show any obvious problems.

from moonshine-sdk-installer.

I think we're talking about two different places here.

MSDKI never setup %GIT_HOME%\bin\git config --global http.sslCAInfo configuration but Moonshine-IDE. I changed in the temporary environment generation command in Moonshine-IDE that match the newer sslCAInfo setup command. I don't expect this to be update after MSDKI Git installation.

I re-tested Moonshine-IDE generated .cmd environment-setup file, and this seems properly setup the sslCAInfo value, when tested on a command-prompt:

from moonshine-sdk-installer.

I retested this with Moonshine Development 3.3.4 Build 1399, and I confirmed that the global config value is not set and the ming64 error still triggers.

For now, I bumped this issue to the next release. My preference would be to either:

• Set the global config value in MSDKI so that the "install" logic is together
• Set the config value for the session only as part of the environment setup. I'll create a Moonshine issue for this (update - added). I'm not sure whether this solution is possible, but it would allow us to use the MoonshineSDK Git for Moonshine without interfering with an external installation.

from moonshine-sdk-installer.