From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp-out-no.shaw.ca (smtp-out-no.shaw.ca [64.59.134.13]) by sourceware.org (Postfix) with ESMTPS id 22A8B385780A for ; Fri, 15 Jan 2021 17:09:14 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 22A8B385780A Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=SystematicSw.ab.ca Authentication-Results: sourceware.org; spf=none smtp.mailfrom=brian.inglis@systematicsw.ab.ca Received: from [192.168.1.104] ([24.64.172.44]) by shaw.ca with ESMTP id 0Sb2lmjlmtdld0Sb3l1caS; Fri, 15 Jan 2021 10:09:13 -0700 X-Authority-Analysis: v=2.4 cv=INe8tijG c=1 sm=1 tr=0 ts=6001cc39 a=kiZT5GMN3KAWqtYcXc+/4Q==:117 a=kiZT5GMN3KAWqtYcXc+/4Q==:17 a=IkcTkHD0fZMA:10 a=yMhMjlubAAAA:8 a=nEG_7a5GlngxQ6F76wQA:9 a=P6LbKte3hMXa3s-j:21 a=QEXdDO2ut3YA:10 Reply-To: cygwin@cygwin.com To: cygwin@cygwin.com References: <638366959.5124927.1610072027608.ref@mail.yahoo.com> <638366959.5124927.1610072027608@mail.yahoo.com> <87im87a03i.fsf@Rainer.invalid> <718595507.5310863.1610134359370@mail.yahoo.com> <1162682432.20210109052742@yandex.ru> <810235038.835431.1610520138584@mail.yahoo.com> <466233249.1039707.1610652048289@mail.yahoo.com> <1302787826.1236791.1610663229230@mail.yahoo.com> <529495646.1380750.1610728577484@mail.yahoo.com> From: Brian Inglis Organization: Systematic Software Subject: Re: mysterious GIT failure Message-ID: Date: Fri, 15 Jan 2021 10:09:11 -0700 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.6.1 MIME-Version: 1.0 In-Reply-To: <529495646.1380750.1610728577484@mail.yahoo.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-CA Content-Transfer-Encoding: 8bit X-CMAE-Envelope: MS4xfMnq38UB61gdPC6OEZpBpnHzRiUg05OiRAFTe5BwxL/F5wBFScDMKUOzKL+KZVkcAXzAAw/XSm9gLwiTATkvrJDAjJ/19esLKz9QX46xJ6q1VI6Eh7wW ujz9CXwcNMylnm/NYlO6ZBx0WWKZenvRMWCZxJ0Gv2UgaSnbLzGi35rPci1syRznseh343vJM2ZkwaaE9wCZles2Zqy9UkGLJmc= X-Spam-Status: No, score=-5.7 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, KAM_LAZY_DOMAIN_SECURITY, NICE_REPLY_A, RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_NONE, TXREP autolearn=no autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: cygwin@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jan 2021 17:09:15 -0000 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. > 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.]