X-Recipient: archive-cygwin AT delorie DOT com
X-Original-To: cygwin AT cygwin DOT com
Delivered-To: cygwin AT cygwin DOT com
DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 061C0386F013
Authentication-Results: sourceware.org; dmarc=none (p=none dis=none)
 header.from=SystematicSw.ab.ca
Authentication-Results: sourceware.org;
 spf=none smtp.mailfrom=brian DOT inglis AT systematicsw DOT ab DOT ca
X-Authority-Analysis: v=2.4 cv=LvQsdlRc c=1 sm=1 tr=0 ts=600492e5
 a=kiZT5GMN3KAWqtYcXc+/4Q==:117 a=kiZT5GMN3KAWqtYcXc+/4Q==:17
 a=IkcTkHD0fZMA:10 a=idWnhwH6AAAA:20 a=94nOnFI1EgyDtX4ev68A:9 a=QEXdDO2ut3YA:10
Subject: Re: misterious GIT failure (SOLVED)
To: cygwin AT cygwin DOT com
References: <1742171701 DOT 1391964 DOT 1610730544471 DOT ref AT mail DOT yahoo DOT com>
 <1742171701 DOT 1391964 DOT 1610730544471 AT mail DOT yahoo DOT com>
 <03cc5513-8a2c-d9cc-6b71-e0c2df0125ed AT SystematicSw DOT ab DOT ca>
 <449114268 DOT 20210117211118 AT yandex DOT ru>
From: Brian Inglis <Brian DOT Inglis AT SystematicSw DOT ab DOT ca>
Organization: Systematic Software
Message-ID: <2213ecae-52ec-4148-9370-78b846fb26cc@SystematicSw.ab.ca>
Date: Sun, 17 Jan 2021 12:41:24 -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: <449114268.20210117211118@yandex.ru>
Content-Language: en-CA
X-CMAE-Envelope: MS4xfLCgWaZZH10EtGyhVtmFfyHjAGwslBgwB/OvBej4SIE4JFENnzIxk50HCqToNjLV3zwAejcQ1dWXfM3CCLGa+61AC4Ahl+5Bd1jTJqc67B1Ku4wmJifL
 MIrynw4dYb4HpDy4xTMJ/Do5DQkqeiWGmm+0zpPmxtkugOVEauucDZ5EjVjRKxNidGw/97mUQAYVt0PyYXbUCQWnxGRwG4XDgNg=
X-Spam-Status: No, score=-5.8 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=ham 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 AT cygwin DOT com
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe: <https://cygwin.com/mailman/options/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe>
List-Archive: <https://cygwin.com/pipermail/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe: <https://cygwin.com/mailman/listinfo/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
Reply-To: cygwin AT cygwin DOT com
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Errors-To: cygwin-bounces AT cygwin DOT com
Sender: "Cygwin" <cygwin-bounces AT cygwin DOT com>

On 2021-01-17 11:11, Andrey Repin wrote:
> Greetings, Brian Inglis!
>> 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.
> 
> Can you provide examples? I find cygpath output satisfying so far, with
> readlink if needs that bad.

Sorry, it's been a few years now - there were a few issues testing various paths 
using various directories and links that neither readlink nor realpath resolved 
absolutely and correctly, so I added the cygpath to and fro to give a consistent 
path to support ordering and duplicate checking.

-- 
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.]
--
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