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:mime-version:date:message-id:subject:from:to :content-type; q=dns; s=default; b=jC3X3+RQC+VJK78PpvQSRJ22C3d/7 327B2ffHvHTyEhFfH8JE3wPqYpfF/kwhU5GOKbYCVfGCvuNNXI2BC6D+8ZI3F0uy tUaDSL2cKJDTx4qIi+igKA1+hz2CTkuxmZDVig106n54o16tjeu/TIndsNDqxybf Um+XY+paQsNEgQ= 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:mime-version:date:message-id:subject:from:to :content-type; s=default; bh=rmQG57UT7J1iSSyMpCx5cVtaIl8=; b=ehT 5d7L/OOGMUmhj0sqqn9ChNgQsnDmJXVlVc6+98qQclBc6JtrpYfXVngLVNrlFR2W UtZfZfgo88r/Ng0BvaNe25dIXo73s2UQYCL+k0Dfc9rTRqnPHTW9M4jt21i5fkFN hTcnw6EXlYd9aEGBLB0SKtcw+XKQBWyHWDnLkiFM= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , 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.8 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mail-lb0-f174.google.com MIME-Version: 1.0 X-Received: by 10.152.9.2 with SMTP id v2mr3583606laa.67.1423239727472; Fri, 06 Feb 2015 08:22:07 -0800 (PST) Date: Fri, 6 Feb 2015 17:22:07 +0100 Message-ID: Subject: Group execute permission regression (??): causing problem in fossil. From: Jan Nijtmans To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=UTF-8 X-IsSubscribed: yes Hi All, Starting with the upgrade to Cygwin (latest: 1.7.34), fossil started to behave strangely: Every file committed to a fossil repository suddenly had the execute permission bit set! With 1.7.33 this didn't happen. The cause of this problem was that apparently starting with Cygwin 1.7.34, the group permission bit in some directories is always set, and cannot be unset. For example from my checked-out fossil repository: nijtmaj /workspace/fossil $ ls -la .fossil-settings total 20 drwxrwxr-x+ 1 nijtmaj None 0 Feb 6 16:48 . drwxrwxr-x+ 1 nijtmaj None 0 Feb 6 16:48 .. -rw-rwxr--+ 1 nijtmaj None 140 Feb 6 16:48 clean-glob -rw-rwxr--+ 1 nijtmaj None 55 Feb 6 16:48 encoding-glob -rw-rwxr--+ 1 nijtmaj None 61 Feb 6 16:48 ignore-glob -rw-rwxr--+ 1 nijtmaj None 61 Feb 6 16:48 keep-glob nijtmaj /workspace/fossil $ chmod a-x .fossil-settings/* nijtmaj /workspace/fossil $ ls -la .fossil-settings total 20 drwxrwxr-x+ 1 nijtmaj None 0 Feb 6 16:48 . drwxrwxr-x+ 1 nijtmaj None 0 Feb 6 16:48 .. -rw-rwxr--+ 1 nijtmaj None 140 Feb 6 16:48 clean-glob -rw-rwxr--+ 1 nijtmaj None 55 Feb 6 16:48 encoding-glob -rw-rwxr--+ 1 nijtmaj None 61 Feb 6 16:48 ignore-glob -rw-rwxr--+ 1 nijtmaj None 61 Feb 6 16:48 keep-glob For some reason, the group execute permission bit of those files is always set, and cannot be unset. When fossil commits a file, it looks at the current file permissions (either user, group or other) here: that's where the sudden change comes from. A workaround for this problem is committed in fossil now, but it's puzzling to me why this happens. Not all directories behave like this, so it probably has a relation with permissions ....... Hoping someone can shine a light on that! Regards, Jan Nijtmans -- 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