From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7739 invoked by alias); 25 Oct 2012 15:54:20 -0000 Received: (qmail 7731 invoked by uid 22791); 25 Oct 2012 15:54:19 -0000 X-SWARE-Spam-Status: No, hits=1.8 required=5.0 tests=AWL,BAYES_00,BOTNET,KHOP_THREADED,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_NO,RCVD_IN_HOSTKARMA_YE X-Spam-Check-By: sourceware.org Received: from vms173009pub.verizon.net (HELO vms173009pub.verizon.net) (206.46.173.9) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 25 Oct 2012 15:54:14 +0000 Received: from [192.168.1.231] ([unknown] [108.20.163.251]) by vms173009.mailsrvcs.net (Sun Java(tm) System Messaging Server 7u2-7.02 32bit (built Apr 16 2009)) with ESMTPA id <0MCG004ZHHHZPRC0@vms173009.mailsrvcs.net> for cygwin@cygwin.com; Thu, 25 Oct 2012 10:54:04 -0500 (CDT) Message-id: <50896098.8020309@cygwin.com> Date: Thu, 25 Oct 2012 15:54:00 -0000 From: "Larry Hall (Cygwin)" Reply-to: cygwin@cygwin.com User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121010 Thunderbird/16.0.1 MIME-version: 1.0 To: cygwin@cygwin.com Subject: Re: Cygwin 1.7.17 breaks unattended setup References: <5088898B.3050606@cygwin.com> In-reply-to: Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7bit Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com X-SW-Source: 2012-10/txt/msg00414.txt.bz2 On 10/25/2012 3:07 AM, Achim Gratz wrote: > Larry Hall (Cygwin 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. I'm not saying that setup.ini isn't triggering the bug in 'setup.exe' but I still contend if 'setup.exe' can't function properly in unattended mode due to an external change then this is a bug within 'setup.exe', no matter how long it has been since its last release. Of course, a motivated individual looking for a workaround could certainly remove the newest packages from their local 'setup.ini' file to see if that helps. If so, one could then narrow in on the package that's causing unattended mode to fail. -- Larry _____________________________________________________________________ A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email? -- 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