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 CCB9D3877023
Authentication-Results: sourceware.org;
 dmarc=pass (p=none dis=none) header.from=yandex.ru
Authentication-Results: sourceware.org;
 spf=pass smtp.mailfrom=anrdaemon AT yandex DOT ru
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail;
 t=1584479101; bh=QBKmED4YAMm7iUMLalJi2oUchRoAYZaKylSljoQXhJs=;
 h=In-Reply-To:Subject:To:Reply-To:From:Message-ID:References:Date;
 b=Ph0bHbAUitMufbyHJrYgcHadwL6oswIgRPia1UbO7bOrv2IKIEGASao+ThePPZNOv
 3g95dud6cOXlf1mi6xfxf28iE4LiA7cDlaBX2AOz54qhD9ACiGjx26Il0ZStYIlbh6
 S7UknUk4tBIsHGjAJu2CCtPH17l6sJZ82ppYS4ww=
Authentication-Results: mxback20o.mail.yandex.net;
 dkim=pass header.i=@yandex.ru
Date: Tue, 17 Mar 2020 23:55:43 +0300
From: Andrey Repin <anrdaemon AT yandex DOT ru>
X-Mailer: The Bat! (v6.8.8) Home
X-Priority: 3 (Normal)
Message-ID: <1326008800.20200317235543@yandex.ru>
To: David Karr <davidmichaelkarr AT gmail DOT com>, cygwin AT cygwin DOT com
Subject: Re: Conflict between Eclipse JGit and Cygwin HOME
In-Reply-To: <CAA5t8VoxA680p7xpOm+GgK5ZejiTuY-RXzuCpc_6TX5H7qAK3Q@mail.gmail.com>
References: <CAA5t8Vo_B+yAwTkUsHFFM1oXo8ntvXduyG-ua-H7oGyenTm=ng AT mail DOT gmail DOT com> 
 <528226091 DOT 20200317040308 AT yandex DOT ru>
 <ea2832cb-21e0-e9cc-1cd1-2328030b65c4 AT SystematicSw DOT ab DOT ca>
 <CAA5t8VoxA680p7xpOm+GgK5ZejiTuY-RXzuCpc_6TX5H7qAK3Q AT mail DOT gmail DOT com>
MIME-Version: 1.0
X-Spam-Status: No, score=1.7 required=5.0 tests=DKIM_SIGNED, DKIM_VALID,
 DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, KAM_THEBAT, RCVD_IN_DNSWL_NONE,
 SPF_HELO_NONE, SPF_PASS autolearn=no autolearn_force=no version=3.4.2
X-Spam-Level: *
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: Cygwin mailing list <cygwin.cygwin.com>
List-Unsubscribe: <http://cygwin.com/mailman/options/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe>
List-Archive: <http://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: <http://cygwin.com/mailman/listinfo/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
Reply-To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset="cp1250"
Errors-To: cygwin-bounces AT cygwin DOT com
Sender: "Cygwin" <cygwin-bounces AT cygwin DOT com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by delorie.com id 02HL5aBL023578

Greetings, David Karr!

>>
>> You problem seems to be with your Windows network profile and Windows
>> programs,
>> nothing to do with Cygwin.
>> Fixing the former will probably fix the latter.
>>

> If it wasn't obvious, I'm trying to find a solution, not assign blame.

I, personally, offered at least one solution that I've tested myself.
Cygwin Git do not play nice with naive programs over local filesystem. UNC
paths are a lil' bit better in this regard.
But Git-for-Windows will certainly work better with native tools.

> Of course it has "something to do with Cygwin", because I'm using it,

It should have something to do with the air, because you are breathing it…
I hope you get the analogy.

> and Cygwin and WIndows are using a shared resource, the "HOME" variable.

No, Windows do NOT use %HOME% in any way, shape, or form.

> Cygwin and Windows try to use it for different purposes.  There's nothing I
> can do about the "Windows network profile".

Windows only using

1. %HOMEDRIVE%%HOMEPATH%
2. %HOMESHARE%
3. %USERPROFILE%

as far as I recall.
These are all different variables pointing to (potentially) different
locations. Supposedly, all of them exist (if defined). (I may be wrong, but my
12 years of experience with domain networks tell me this should be true.)

>> But if your work infrastructure does not yet support W10 1809 (do you
>> really
>> mean that release, not the current 1909 release?) you should not have
>> upgraded,
>> and any breakage is down to you.
>>

> Again, you took this as me trying to assign blame, which is pointless.

Again, no. We made a mission statement, but at the same time we offered a
solution.

> Yes, I meant 1809, and although I performed the upgrade manually, it would
> have been done automatically in the near future if I hadn't, so there was
> no choice there.


>> For Cygwin options see:
>>
>> https://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-mapping-nsswitch-desc


> Yes, I've seen that, and considered my options there, but I don't think
> that will address this situation.  The problem is the contents of the
> "HOME" variable. It doesn't matter where my Cygwin HOME directory actually
> resides.

See above. And test your assumptions.


-- 
With best regards,
Andrey Repin
Tuesday, March 17, 2020 23:47:29

Sorry for my terrible english...
--
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