From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 117259 invoked by alias); 10 Jul 2017 23:17:56 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 117250 invoked by uid 89); 10 Jul 2017 23:17:55 -0000 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 Received: from mailsrv.cs.umass.edu (HELO mailsrv.cs.umass.edu) (128.119.240.136) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 10 Jul 2017 23:17:54 +0000 Received: from [192.168.0.4] (c-24-62-203-86.hsd1.ma.comcast.net [24.62.203.86]) by mailsrv.cs.umass.edu (Postfix) with ESMTPSA id BCB11401D998; Mon, 10 Jul 2017 19:17:52 -0400 (EDT) Reply-To: moss@cs.umass.edu Subject: Re: Request to the git maintainer References: <87a84cxcos.fsf@Rainer.invalid> <64cc57cf-09c7-6225-963f-9adacb7d03af@cs.umass.edu> <5b9b894856c27a28ce349b3689fe8751@mail.kylheku.com> To: cygwin@cygwin.com From: Eliot Moss Message-ID: Date: Mon, 10 Jul 2017 23:17:00 -0000 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 X-SW-Source: 2017-07/txt/msg00158.txt.bz2 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