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=nYyDvFRoUW0m19Ox60NUvEMoAMeJUFo6EdFzxIxTPCels4+SbROUf
	GheSXHE3GD7+y5gv5jW7p/m9mnEFDJUDCV4UtEfqE7c8GwdhOokfIiS2HmUyLQLt
	s3XIVxBrHzS3Mla75Wk69Evb9roiBA3pfGfqUVzQ+79G8lBT9IQ6Yk=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Mon, 10 Nov 2014 12:45:52 +0100
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 1.7.33-0.8
Message-ID: <20141110114552.GF2782@calimero.vinschen.de>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <announce.20141107091107.GS28195@calimero.vinschen.de> <545FF889.2020503@tiscali.co.uk>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;	protocol="application/pgp-signature"; boundary="7mxbaLlpDEyR1+x6"
Content-Disposition: inline
In-Reply-To: <545FF889.2020503@tiscali.co.uk>
User-Agent: Mutt/1.5.23 (2014-03-12)

--7mxbaLlpDEyR1+x6
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Nov  9 23:28, David Stacey wrote:
> On 07/11/2014 09:11, Corinna Vinschen wrote:
> >I just released a 8th TEST version of the next upcoming Cygwin release,
> >1.7.33-0.8.
>=20
> I've done a little testing, and the only casualty so far seems to be the
> bash post install script. If you perform a clean install of Cygwin (x86 or
> x86_64) and install just the base packages with a test version of cygwin,
> then the bash post install script always exits with return code 1. The li=
nks
> '/dev/stdin', '/dev/stdout' and '/dev/stderr' are not created.
>=20
> This is rectified by either invoking mintty and running the bash post
> install script manually, or by running setup again, keeping the test vers=
ion
> of cygwin and getting setup to run the bash post install script.
>=20
> This problem is not observed when installing cygwin-1.7.32-1; in this
> instance the bash post install script runs correctly and the three links =
are
> created.
>=20
> Version numbers are as follows:
>=20
>     setup 2.852
>     cygwin-1.7.33-0.8 (also -0.4; I haven't tried the other test versions)
>     bash-4.1.17-9
>=20
> Tested under Windows 7 Ultimate SP1 64-bit.
>=20
> Hope this is helpful,

This is a dependency problem.  Whatever you observed in terms of 1.7.32
vs. 1.7.33-0.x, it has nothing to do with Cygwin itself.  The problem is
that a real /dev directory hasn't been created when the bash script is
called, because the base-cygwin postinstall script, which creates the
directory, hasn't been run before running the bash postinstall script.

This is some problem in the upset perl script on cygwin.com which really
needs investigation.


Corinna

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

--7mxbaLlpDEyR1+x6
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJUYKVwAAoJEPU2Bp2uRE+godwQAI7QzxSWPnBUfeS8GuTMQT0w
DwGKE5qBjy0U8m2gd5rBlyKngkyjIrB9JG/FBPsTzH0kzhITb3pcieHFcbUybxOX
pU0MZjTNMQJwzfH/CQE3UV1ASZXbMgwRRD0ifqZOgu0G7DHwdvSKSl8BtPqYdRIb
3wYz0fu1gbKIVenahSYxC+qEw5QUhw6QkU7ZuJa5IFJD4aqyJhmPEniiPwt3+bKr
bgSG6d/MgpW8D3uzVImSxmhQCCTWg7bMvP1UpmzCSHewsgDPEPPdF4HxmqJ3OCJg
cPmMWEzsbLbL2x7HaNvU60du40ANzlpW//6dJlaCgSkQ9upU3LBnXD6i2KwEgGup
146kZD+VCNjPPbl5+JjGP53WSQmp+JPWe6rUiSNDPJ8O6v1p++DKHgi/fush2Gw6
EKdVbyn3Tv9Gcs3NNHf1d//AWDrTmj90whJXWqNBdLDmUA+SHam0wo0QdJchuh60
mVX820eg0t+3RcRP/MBzeHpPEXbtWvt+X9MxA404zt6olxhOPOHVWOwhF2gXEGba
AJ0pqAGptVRDNYmeEFpAwCqzHCHRAMeGRCVQiANu3QgaHBCX7BEE82b6iucpmHWc
Zmd6PvkttScUAbsw66gJu5NOGbtE22T8hQ/QhzON56ooZpceFpX1XMi+/vEzYTEq
KY+VceNTEgdjEOk+ZuXi
=EGPk
-----END PGP SIGNATURE-----

--7mxbaLlpDEyR1+x6--