X-Recipient: archive-cygwin@delorie.com
X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 	tests=BAYES_00,SPF_HELO_PASS
X-Spam-Check-By: sourceware.org
To: cygwin@cygwin.com
From: Steve Bray <steve4578@comcast.net>
Subject: Re: svn: Can't change perms of file Permission denied
Date: Thu, 18 Mar 2010 22:10:07 -0500
Lines: 29
Message-ID: <hnupug$mep$1@dough.gmane.org>
References: <B40B1D23235C0246B5B5F02A1ABF5B064403040A@naeapaxrez02v.nadsusea.nads.navy.mil> <97E8FD1108ECB64FB813E8E4AC7FCD6A058738A9@naeapaxrez02v.nadsusea.nads.navy.mil> <8465FB3F14FB409AA328076156128DD3@phoenix>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.8) Gecko/20100301 Fedora/3.0.3-1.fc12 Lightning/1.0b2pre Thunderbird/3.0.3
In-Reply-To: <8465FB3F14FB409AA328076156128DD3@phoenix>
X-IsSubscribed: yes
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie.com@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

On 03/18/2010 05:06 PM, Jason Pyeron wrote:
> It seams that svn needs to be able to write the DAC, and if it cannot then svn
> up cannot work. This seems to be not the case in the past (or was there some
> magic voodoo on my old system?)
>
> Any suggestions on where to start?
>
> Granting Full on the share and the directory mitigated this issue. I am unable
> to keep full control on the share, and previously we had Modify/Change on the
> share and svn was working.
>
This may be the issue that I previously reported

Cygwin 1.7.1 breaks git on netapp shared drives
http://www.cygwin.com/ml/cygwin/2010-01/msg01146.html

A secured share drive has inherited acls without permissions to change 
the permissions.  This will be very common on a Windows shared drive but 
does not occur with POSIX.  In the transition from cygwin 1.5 to 1.7 it 
appears that they try harder to use acls.  If they find them they try to 
use them ... but on these shared drives the users do not have 
permissions to change them.  Any application that attempts to change 
them now fails, git, svn, you name it.  We now need to mount the shared 
drives with the noacls flag so cygwin stops trying to change acls even 
though it does not have permission.

Perhaps at mount, if the top directory has inherited permissions that 
lack permission to change permissions then it could revert to the noacls 
behavior.


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

