X-Recipient: archive-cygwin@delorie.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:reply-to:subject:references:to:from:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=UKgaLeG4KpoLtRbw
	NnDQcN3YtD+cWIicaPFuPOurcZUry6Atofzp4iAqy1o5w7xo5kAmdExidoCknp67
	R9DDNxMmhkZCNQzGFQHqI3BnSevoNt4I7Jo828SHRtH8z9wQhCJM2B1C1ei+q+t9
	uO2fDlrE2ZxJM1bNMk9UAJGaf2g=
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:reply-to:subject:references:to:from:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=6WMbrQ3s9BjyLFT9e8fBAw
	lp0Hs=; b=drWqBjHRv/iEflkwvohridsgOv/1JFTE1yt8bHxWgRvhNWs4LGcb8T
	UIFZi5+UejyAyLq3N/SU/z+yKfeUCwRrV8lnZGSJrPgdnpmn+FyZ4fnvDqeUTWwq
	8nv3T330spMZZAkTimtaIH2zYEDti97yI8G6CT3nF3CxGJzNK7Yco=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=0.8 required=5.0 tests=AWL,BAYES_20,KAM_LAZY_DOMAIN_SECURITY,RP_MATCHES_RCVD autolearn=no version=3.3.2 spammy=kylheku, kaz, H*Ad:D*cs.umass.edu, H*Ad:D*umass.edu
X-HELO: mailsrv.cs.umass.edu
Reply-To: moss@cs.umass.edu
Subject: Re: Request to the git maintainer
References: <b5a70575-b81b-12c1-aad3-b100dd7acaa0@cs.umass.edu> <87a84cxcos.fsf@Rainer.invalid> <64cc57cf-09c7-6225-963f-9adacb7d03af@cs.umass.edu> <5b9b894856c27a28ce349b3689fe8751@mail.kylheku.com>
To: cygwin@cygwin.com
From: Eliot Moss <moss@cs.umass.edu>
Message-ID: <aa3bdabb-5e98-ada9-f033-15b675dee069@cs.umass.edu>
Date: Mon, 10 Jul 2017 19:17:50 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <5b9b894856c27a28ce349b3689fe8751@mail.kylheku.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

On 7/10/2017 6:27 PM, Kaz Kylheku wrote:
> On 10.07.2017 14:02, Eliot Moss wrote:
>> On 7/10/2017 4:24 PM, Achim Gratz wrote:

> You can't ask every vendor of everything that you have installed
> or "git pulled" to fix their permissions because your backup program
> has bizarre limitations.

I'm not asking "every vendor".  I'm asking a limited number of
cygwin port maintainers (and so far only one specifically).

CrashPlan does not have "bizarre" limitations -- it quite
naturally has some difficulty if a file's access does not grant
it permission.

The permissions on these files is what is bizarre.  There is no
good reason they should deny read access.

Windows does not really have an equivalent of "root" that can
access anything, so there is not really any privilege I can
give the backup tool that is guaranteed to work in all cases.

I can fix the access mode manually, but every time there is an
update to the package, it will revert, so that's not a great
solution.

Beyond that, I'm not going to argue with you, Kaz.

Regards to you all -- Eliot

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

