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.12]) by sourceware.org (Postfix) with ESMTPS id 14B16398583F for ; Fri, 15 Jan 2021 17:30:00 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 14B16398583F 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 0Sv8lmtCltdld0Sv9l1jYn; Fri, 15 Jan 2021 10:29:59 -0700 X-Authority-Analysis: v=2.4 cv=INe8tijG c=1 sm=1 tr=0 ts=6001d117 a=kiZT5GMN3KAWqtYcXc+/4Q==:117 a=kiZT5GMN3KAWqtYcXc+/4Q==:17 a=IkcTkHD0fZMA:10 a=idWnhwH6AAAA:20 a=94nOnFI1EgyDtX4ev68A:9 a=QEXdDO2ut3YA:10 Reply-To: cygwin@cygwin.com To: cygwin@cygwin.com References: <1742171701.1391964.1610730544471.ref@mail.yahoo.com> <1742171701.1391964.1610730544471@mail.yahoo.com> From: Brian Inglis Organization: Systematic Software Subject: Re: misterious GIT failure (SOLVED) Message-ID: <03cc5513-8a2c-d9cc-6b71-e0c2df0125ed@SystematicSw.ab.ca> Date: Fri, 15 Jan 2021 10:29:58 -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: <1742171701.1391964.1610730544471@mail.yahoo.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-CA Content-Transfer-Encoding: 8bit X-CMAE-Envelope: MS4xfCb1LJfROsIS0lSCgSVc1jI/0bPoCB4EkD87uGl+MMXterrAKp2Z2P8byCaEDN5BwTHpaC0+oiKNzQBf/rki6Es5dSR+79f4/TiCT2s32aY3riU4ZhSS WuThzXxncbZfF0TnrZfPcAHj7XjeUeN9L2wLkBWj0ZGQioa/slIOTb5t2ndBWi3ychy6cHaDCAYNQShTsqoMhKv8ErmioEP+PrU= 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:30:01 -0000 On Friday, January 15, 2021, 11:36:28 AM EST, matthew patton via Cygwin wrote: > On 2021-01-15 10:09, matthew patton via Cygwin wrote: >> Ken Brown wrote: >>> Do you by any chance have symlinks in your PATH? 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: >> 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/fstab >> C:/Users /home none binary,user 0 0 > 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 Resolving Cygwin paths is best done using readlink or realpath followed by cygpath -alm then cygpath -auU to get canonical paths, as neither realpath nor cygpath do the complete job under Cygwin. -- 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.]