Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Subject: Setup failures over the last few days
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Date: Fri, 10 May 2002 21:24:13 +1000
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
Message-ID: <FC169E059D1A0442A04C40F86D9BA7600C6036@itdomain003.itdomain.net.au>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
From: "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To: "Cygwin" <cygwin AT sources DOT redhat DOT com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g4ABOcx26190

Short answer: use
http://www.cygwin.com/setup-snapshots/setup-20020510.exe.

Long answer: The new MD5 rule + the number of packages which increased
recently caused a yacc parsing failure. This has been corrected in CVS
for the pre-release version and for HEAD.

As I've seen no bug reports on the UPX support, I've started compressing
setup with UPX as a matter of routine.

Please, try the setup linked above, and if you have any errors let me
know. AFAICT though, it should be ready for widespread use now.

I'm not planning on updating the current setup, as 
1) It was about to be obsoleted anyway and
2) Users will still have the stack failure/crash anyway, so they will
have to update manually regardless.

Rob

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/