DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=u5505V1u9/AWM3sI8IOva1fcOdaRqWykRDk8puzhNmpRcfX3W1KGC
	rpFPCIrKsNAKK3CLSX3NrE6w/VDmaNO47D0LK1X06SpRo62KM/DdXbXsiytuYIMM
	3pis77XlMXLBlBpJP7xN2F1WkOxNvxuFM6NgRHLQ2E4A+3k94iJQX4=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Tue, 10 Feb 2015 10:30:30 +0100
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Fossil 1.30 [Was: Group execute permission regression (??): causing problem in fossil.]
Message-ID: <20150210093030.GD15989@calimero.vinschen.de>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <CAO1jNwvAUJ0RBBL992c3i4P9AsrEvtbtoL1hJhk67wyx101-XQ@mail.gmail.com> <20150209134353.GA13592@calimero.vinschen.de> <871tlyk7cz.fsf_-_@picasso.cante.net>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;	protocol="application/pgp-signature"; boundary="SFyWQ0h3ruR435lw"
Content-Disposition: inline
In-Reply-To: <871tlyk7cz.fsf_-_@picasso.cante.net>
User-Agent: Mutt/1.5.23 (2014-03-12)

--SFyWQ0h3ruR435lw
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi Jari,

On Feb 10 01:11, Jari Aalto wrote:
> 2015-02-09 15:43 Corinna Vinschen
> <corinna-cygwin@cygwin.com>:
> | On Feb  9 11:10, Jan Nijtmans wrote:
> |
> | > 2015-02-09 10:23 GMT+01:00 Corinna Vinschen <corinna-cygwin@cygwin.co=
m>:
> | > > 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 i=
t 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 f=
ix
> | > to be available soon.
>=20
> Uploading new 1.31 in couple of days with fix included.
>=20
> Thanks Corinna for the CC,
> Jari

Would you mind terribly to start converting your build systems to
cygport with this package?  In the long run we're still trying to move
to an automated build system which would profit a lot from using a
unified build method.  If you need help, feel free to discuss on the
cygwinb-apps mailing list.


Thanks,
Corinna

--=20
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

--SFyWQ0h3ruR435lw
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBAgAGBQJU2c+2AAoJEPU2Bp2uRE+gExQQAJMgvgSejJxpWh+M8tdGuVwa
+T+4lb71zplgOSg4tG5qMgjGJS9pEMoazBaLMmrGkn7gtM39UIbIPkeFQ0TT9u86
djSz30OtDXvpPs4RPg9rSACCR9Tuphu0fF1Ug75r8cSeCFE18qxEse/ruXZR9SHa
BrspaTAmxRF6gMQzzxuhLGeZxlmIjt8GSg0uwBCLvdXSOC8FHLYYIfVJGfYnfRku
mVVPRqzjqLgrPl0F2x4UTOc+hGGMHBZWoHhEANbX7nyPWWPggdZMIx7VDJgXxzZd
0b6Xgu3b0/LDEDTT1Rk9tnuBrgkpuVsaiC4jreGPGRG8OC6ybsPuY4l2555tPmjF
5c3Laoi9il+q3Zov2Uhhiz+/4B0uEtQ7b7KOLN4EIuMGveQYTs4zAn5dZPk6buav
xxMZUgdVSTnggAJd2EJOddfPhpfkIaAL/zB9Pwd+OslxnH62C2zLaUF3Gj35jYve
9CfXEXDB2m0nICM9+Y/OjrkeH7BbloI1mZGpSNbQfTfV6guDdE7EGiLariVswHFd
hIy/+uKU3NrIW/KJqRDmAr0oIVtALBH16lYhEV7SBphnTTxtAS+LLzLKMW/+k+RG
9Ky/OlhDkHMIZ/22/kVBuqMu38MWpgXUJYXqMyM9VbB1W2u1BqbmwrLvMcBL7mcb
1t2t0hMkJqpqh9kd0MAJ
=wf7x
-----END PGP SIGNATURE-----

--SFyWQ0h3ruR435lw--