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 A7F463840C2A
Authentication-Results: sourceware.org;
 dmarc=none (p=none dis=none) header.from=cs.umass.edu
Authentication-Results: sourceware.org;
 spf=pass smtp.mailfrom=moss AT cs DOT umass DOT edu
Subject: Re: Native symbolic link behavior is broken and makes backups using
 Cygwin command line tools impossible
To: "Matt D." <codespunk AT gmail DOT com>
References: <CAC+X2=J-mKZH7WAdt2RQocqP+4rUqSkGi-acDC7U3N=uu7QGDA AT mail DOT gmail DOT com>
 <1d853aa0-4cbe-b92c-8d9f-53fc72371a7b AT SystematicSw DOT ab DOT ca>
 <CAC+X2=L2tCUSUYreh2oTSt33Zn295Boru6eAPfkckksKXnB4vQ AT mail DOT gmail DOT com>
 <2f9a63f8-37e3-5ea0-1541-608cf59faffa AT cs DOT umass DOT edu>
 <CAC+X2=L-sBmgi_OoFVjJtpPp6MszHGH8ycEiOo4V1NNbWDAP-A AT mail DOT gmail DOT com>
From: Eliot Moss <moss AT cs DOT umass DOT edu>
Message-ID: <b764a832-82c7-b418-530e-8954c540d4f7@cs.umass.edu>
Date: Mon, 4 Jan 2021 11:32:40 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101
 Thunderbird/68.12.1
MIME-Version: 1.0
In-Reply-To: <CAC+X2=L-sBmgi_OoFVjJtpPp6MszHGH8ycEiOo4V1NNbWDAP-A@mail.gmail.com>
Content-Language: en-US
X-Spam-Status: No, score=-3.0 required=5.0 tests=BAYES_00, JMQ_SPF_NEUTRAL,
 KAM_DMARC_STATUS, NICE_REPLY_A, RCVD_IN_DNSWL_LOW, SPF_HELO_NONE, SPF_PASS,
 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: moss AT cs DOT umass DOT edu
Cc: 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 1/4/2021 10:27 AM, Matt D. via Cygwin wrote:
 > I think there is a misunderstanding with how to set up your
 > environment to reproduce my test cases. I did state in the subject
 > "native symbolic links" but I can see that this can be misinterpreted
 > and I should have clarified.
 >
 > I am using symbolic links native to Windows. My CYGWIN environment
 > variable has been set to "winsymlinks:nativestrict" and my account has
 > permission to make symbolic links. This is an issue specifically with
 > Cygwin; I have no problems making links at the windows command line.
 > Cygwin also does not have a problem making symbolic links-- if the
 > target already exists. The issue is that I cannot create native
 > symbolic links with Cygwin for targets that DON'T exist.
 >
 > The normal behavior for both Windows and Linux is to create the
 > symbolic link whether the target exists or not. I don't know why
 > Cygwin fails to do this only for native Windows symbolic links. It
 > does not have a problem creating links to any target with the default
 > Cygwin (non-Windows) symbolic links.

Ok, I see the behavior now that you are talking about.  You can get it with ln
without any need for cp.  With winsymlinks:nativestrict, if I do:

ln -s foo bar

and foo does not exist, it refuses to create the link.  As you found, it also
refuses to cp it.  However, I _was_ able to mv it.

Regards - Eliot
--
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