X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:date:subject:message-id:references
	:in-reply-to:content-type:content-transfer-encoding
	:mime-version; q=dns; s=default; b=Ym7Z5QWBN14+KqmrOVsex6desBB2G
	vNa4/ytzjHUxzZlfl5ZVs479sU0AHQ2vd9io4U4SXi5ttrFaxzWfLFARDS5m5vIO
	siHjoUPUxVwUDY1tf1Lb6D63P4IwcS44Zi7HUME0dLu4eDa/8iqndTyq3lpLBUah
	7/GARjuRqxX51M=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:date:subject:message-id:references
	:in-reply-to:content-type:content-transfer-encoding
	:mime-version; s=default; bh=hPNCJfqxka46VTNHoVfOjUbTxS8=; b=xlC
	ehzAYhupPFkfkath7nM2Uz/PXQC769NFc4qnF5aPJ5fZx0H1zID6LqVf9IQNkQOe
	nP4zHig7xngKMfcJpA44MYsc7ptuJfAykwFYWeanzQDUfKibvude+YJyjUi/amhj
	7jdEPUiETLWk2aU0n2rlvtonAFYA9W9cPyq3px1s=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=0.5 required=5.0 tests=AWL,BAYES_20,SPF_HELO_PASS,SPF_PASS,T_RP_MATCHES_RCVD autolearn=ham version=3.3.2
X-HELO: mail.voltage.com
From: Phil Smith <phil AT voltage DOT com>
To: "cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
Date: Mon, 30 Mar 2015 07:54:15 -0700
Subject: RE: Possible chmod problem with a path [WARNING: SPF validation failed]
Message-ID: <84BCCD71182F0046BCD2FB054FE52379197703FDF7@HQMAILSVR02.voltage.com>
References: <84BCCD71182F0046BCD2FB054FE52379197703FDDD AT HQMAILSVR02 DOT voltage DOT com> <131547857 DOT 20150330172345 AT yandex DOT ru>
In-Reply-To: <131547857.20150330172345@yandex.ru>
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
X-IsSubscribed: yes
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id t2UEt4YE005862

Thanks for the reply. Some thoughts:

>Please use Cygwin paths with Cygwin tools.
>Windows paths are not guaranteed to work with every Cygwin tool.

This is scripted, and while I can hack it to use Cygwin paths, it probably shouldn't be lying to me, saying that it worked. And it did work before, still does with older Cygwin (on another machine).

>What you are doing may or may not work, depends, if you are using Cygwin or
>native Subversion client.
>In either case, it isn't very bright idea to enforce POSIX access mask outside
>Cygwin tree, unless you know what you are doing and absolutely need it.
>From your description, you don't need it at all.

I'm not actually trying to enforce POSIX anything--I'm trying to be able to read the build artifacts, which were put there via mv and cp. The compiler is native Windows, isn't creating the artifacts with any special permissions. So there's actually another mystery, which is why the artifacts don't have the right permissions in the first place. With the cobbled-together environment (CMake, the Dignus compiler, Cygwin) this may not be really diagnosable, I realized. I was hoping that there was some clue in the fact that the path makes a difference.

SVN client is Tortoise.

I have done a fresh checkout and the problem persists, so it isn't some weirdness with a tainted file in the source tree, I don't think.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple