misterious GIT failure (SOLVED)

matthew patton pattonme@yahoo.com
Fri Jan 15 17:09:04 GMT 2021

I excised the 2 symlink-involved PATH elements and now Git runs great with v3.1.5 of the DLL. I'll try one of the snapshots at some point, but I am also tempted to change my Bash function 'addPath()' to fully unroll symlinks before adding. https://github.com/tb3088/shell-environment/blob/master/.functions#L144    On Friday, January 15, 2021, 11:36:28 AM EST, matthew patton via Cygwin <cygwin@cygwin.com> wrote:  
 Ken Brown wrote:> Do you by any chance have symlinks in your PATH?
Yes, the first and 3rd entries are symlinks. I've had these symlinks in my PATH for years.
/home/MP1116/.aws/YYY/bin:/home/MP1116/bin -> .WPHOME/bin/

.aws -> .WPHOME/.aws/.WPHOME -> Dropbox/Work_Projects/XXX
#/etc/fstabC:/Users /home none binary,user 0 0

>  There was a problem reported in early December in which STATUS_IO_REPARSE_TAG_NOT_HANDLED > would sometimes occur when there was a symlink in PATH:

This KB was released 8 December. I installed it on Dec 23 and my git failures started after that date.https://support.microsoft.com/en-us/help/4592449/windows-10-update-kb4592449

Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:    https://cygwin.com/ml/#unsubscribe-simple

More information about the Cygwin mailing list