X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-2.5 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RCVD_NUMERIC_HELO,RP_MATCHES_RCVD,SPF_HELO_PASS
X-Spam-Check-By:	sourceware.org
To:	cygwin AT cygwin DOT com
From:	Achim Gratz <Stromeko AT NexGo DOT DE>
Subject:	Re: Cygwin 1.7.17 breaks unattended setup
Date:	Thu, 25 Oct 2012 07:07:32 +0000 (UTC)
Lines:	26
Message-ID:	<loom.20121025T085528-526@post.gmane.org>
References:	<CAFDeOSmtVFai01VCFcGeCH-19S7AAixtjLb7fW-3iJpq7rBJFQ AT mail DOT gmail DOT com> <5088898B DOT 3050606 AT cygwin DOT com>
Mime-Version:	1.0
User-Agent:	Loom/3.14 (http://gmane.org/)
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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

Larry Hall (Cygwin <reply-to-list-only-lh <at> cygwin.com> writes:
> > As soon as I disable unattended mode (remove the --quiet-mode switch),
> > if I just take all the default settings in the installer GUI and click
> > the Next button a lot, the installation completes just fine.
> 
> Which is why I said the problem is within 'setup.exe' itself.  Regardless
> of whether some external input may be twiddling an internal bug, it's
> still an internal bug.  And given the number of new packages within the
> last week, the chance for one of those to be a contributing factor is
> certainly much higher than for the cygwin package itself.  But we won't
> know for sure what's at the heart of it until someone has a chance to
> debug it.

Setup.exe hasn't changed for a long time.  While that doesn't preclude a bug
within setup.exe itself, I'd suggest looking at setup.ini first.  I'm absolutely
relying on unattended setup and I haven't noticed any problems, much less
recently.  However, I'm rewriting setup.ini since I merge several package
sources into a new install tree.  This also means that the general structure of
setup.ini for Cygwin must still be OK (my script would barf otherwise and I
think upset would be, well, upset as well) and I'm probably not using any of the
packages that trigger the bahaviour.  The only ones that come to mind are some
recent additions that have dots and plus characters in their version part.


Regards,
Achim.


--
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

- Raw text -