Conflict between Eclipse JGit and Cygwin HOME

[Andrey Repin]

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