On 2025-07-26 07:45, Jon Turney via Cygwin-apps wrote:
On 21/07/2025 22:27, Matthew Sheets via Cygwin-apps wrote:
In troubleshooting issues using Cygwin within GitHub runners, one specific
problem scenario identified is when the Cygwin "git" package is installed.
When that happens, Cygwin's Git installation ends up being executed instead of
GitHub's installation of Git, which obviously doesn't have the same setup,
configuration, etc. as GitHub's own internal install of Git.
Usually, these issues can be avoided by simply not including the "git" package
among the list of packages to be installed along with Cygwin [1], but it
appears there are certain cases where Cygwin's "git" package is being pulled
in as a dependency by other Cygwin packages.
Yeah, I've come across this as well.
Unfortunately, there doesn't seem to be a way for a simple action like ours to
register a post-run step to unwind the changes it makes to the path.
The only general work around I found was to add an explicit step at the end to
do 'rm /usr/bin/git' to avoid it being in PATH.
(Obviously you can also ask the action to not modify PATH, but this makes
everything else more awkward)
Please let us know if you find a better solution!
In packages where cygport uses `inherit git` cygclass/GIT_{URI,BRANCH,TAG,REV}
sources, cygport assumes Cygwin git is available as BUILD_REQUIRES, as any other
Windows runner git may misinterpret args.
--
Take care. Thanks, Brian Inglis Calgary, Alberta, Canada
La perfection est atteinte Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add
mais lorsqu'il n'y a plus rien à retrancher but when there is no more to cut
-- Antoine de Saint-Exupéry
