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=b4Pc0KlpvxR75UfSpL/XCpwXb8nMX
	6VbzRGPL8Vh+SEuzfLlJI4vKwh9rJ4rBexdU9XUZmpYOXylTege9qaIwY7sawVLC
	HiKX3Cssao+/bHpJAzqWVhRHF3VgBqXNUz4qmLEW6LmCeXPH4J/ojhjz9Qz+lwrW
	RYUd4G/Qh0enFo=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
MIME-Version: 1.0
Date: Mon, 9 Feb 2015 11:10:51 +0100
Message-ID: <CAO1jNwvAUJ0RBBL992c3i4P9AsrEvtbtoL1hJhk67wyx101-XQ@mail.gmail.com>
Subject: Fossil 1.30 [Was: Group execute permission regression (??): causing problem in fossil.]
From: Jan Nijtmans <jan.nijtmans@gmail.com>
To: cygwin@cygwin.com
Content-Type: text/plain; charset=UTF-8

2015-02-09 10:23 GMT+01:00 Corinna Vinschen <corinna-cygwin@cygwin.com>:
> No worries.  I guess I should revamp the FAQ to add a more generic
>
>   Why do my files have certain group permissions and chmod doesn't help?
>
> entry.  I just didn't expect that this change would create problems with
> other tools than ssh or rlogin :|

A fix for this has been committed in upstream fossil now, pity that it just
missed fossil 1.30. This brings me to the following:

Latest Cygwin-packaged fossil is version 1.29, while fossil 1.30 came out
3 weeks ago. I could prepare a patch for 1.30, if desired. Since 1.29 has
the same problem, I would like to find a new 1.30 version with this fix
to be available soon.

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