[WINDOWS] choco install git and choco upgrade git fail


I need git version 2.26.2, try to upgrade/install fails

It doesn’t show why it failed.


chocolatey advises you to look at the logs https://travis-ci.com/github/KhushrajRathod/TdBuildWin/builds/163014046#L53-L54

I don’t know how the build later halts, however. I imagine it’s a separate issue.

Hi, thanks for replying!
I’m looking at the log, till then there’s a minimal repo here https://travis-ci.com/github/KhushrajRathod/TravisWindowsGitInstallFailure

I suggest dumping the logs, as the error message indicates, to learn more about the failure.

Here’s a build with the log dumped, but note that it exceeds the maximum build length

Try reducing the log verbosity, or only dump the end of the logs; I doubt that the beginning is helpful.

Here’s a truncated log build: https://travis-ci.com/github/KhushrajRathod/TravisWindowsGitInstallFailure/builds/164295877

This seems like the error

2020-05-06 18:18:48,540 3112 [ERROR] - ERROR: Running ["C:\ProgramData\chocolatey\lib\git.install\tools\Git-2.26.2-64-bit.exe" /VERYSILENT /SUPPRESSMSGBOXES /NORESTART /NOCANCEL /SP- /LOG /COMPONENTS="icons,assoc,assoc_sh,ext,ext\shellhere,ext\guihere,gitlfs,icons\quicklaunch" ] was not successful. Exit code was '1'. See log for possible error messages.

I can’t see anything except this :confused:


The log produced by the /LOG option to Windows Git installer should be at $TEMP/Setup Log*.txt.

That said, why do you install git and not upgrade the preinstalled git.install? Because they provide the same software, they may be conflicting with each other.

Sorry, I don’t usually develop for windows, so I didn’t know how chocolatey works :slight_smile:
I’m going to try upgrading git.install and post a log if it fails.

@native-api @BanzaiMan Here’s a build with both git logs, and the chocolatey log dumped: https://travis-ci.com/github/KhushrajRathod/TravisWindowsGitInstallFailure/builds/164876604


Setup cannot continue until you close at least those applications in the list that are marked as “closing is required”.

Shit! I feared so. You cannot do anything with the system-wide Git for Windows installation because Travis uses it itself for its machinery.

You’ll have to install a portable version instead – and invoke it with full path after the installation.

@native-api Hi, thanks for replying :slight_smile:.
I had thought about this earlier, but then I remembered that on a linux/macOS machine you can upgrade bash from within bash. I guess it doesn’t work the same way with windows :confused:. I’ll try the portable version and let you know how it goes. Could this be added to the known issues?

@native-api Thanks for adding this!