public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: mysterious GIT failure
Date: Fri, 15 Jan 2021 10:09:11 -0700	[thread overview]
Message-ID: <bec69ec5-2d84-4ad2-8253-947b4cd766f7@SystematicSw.ab.ca> (raw)
In-Reply-To: <529495646.1380750.1610728577484@mail.yahoo.com>

On 2021-01-15 09:36, matthew patton via Cygwin 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:

Given that you have the same symptom, it is possible that Git-Bash or something 
else you are running in Windows is creating symlinks somewhere, which Cygwin is 
attempting to read while resolving some path search, or opening some directory 
or file entry, so it would seem advisable to download and install the latest 
snapshot DLL.
You could test this by trying to operate with only minimal Cygwin path /usr/bin: 
/bin and git clone into Cygwin /tmp/ or /usr/tmp/ as long as they are not 
mounted on non-Cygwin directories like your /home is, where Windows programs are 
likely to have an impact.

> 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>
Known issue with that update is loss of user and system certs - hopefully only 
from Windows cert store affecting only Windows apps - but could that impact 
anything you are using?

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]

  reply	other threads:[~2021-01-15 17:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <638366959.5124927.1610072027608.ref@mail.yahoo.com>
2021-01-08  2:13 ` misterious " matthew patton
2021-01-08 10:35   ` Adam Dinwoodie
2021-01-08 16:02   ` Achim Gratz
2021-01-08 19:32     ` matthew patton
2021-01-09  2:27       ` Andrey Repin
2021-01-13  6:42         ` matthew patton
2021-01-14 19:20           ` matthew patton
2021-01-14 22:27             ` matthew patton
2021-01-14 23:48               ` Ken Brown
2021-01-15 16:36                 ` matthew patton
2021-01-15 17:09                   ` Brian Inglis [this message]
2021-01-15 17:22                     ` mysterious " matthew patton
2021-01-14 22:42             ` Brian Inglis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bec69ec5-2d84-4ad2-8253-947b4cd766f7@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).