X-Spam-Check-By: sourceware.org Message-ID: <468203D0.9060800@bonhard.uklinux.net> Date: Wed, 27 Jun 2007 07:29:36 +0100 From: fergus User-Agent: Thunderbird 2.0.0.4 (Windows/20070604) MIME-Version: 1.0 To: Cygwin ML CC: fergus Subject: Re: Call for testing: New setup.exe version Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com All of 2.575, 2.573.2.1 and two earlier test versions I tried, 2.562 and 2.558, fail in a way that the current version 2.510.2.2 does not. If you have a perfectly coherent and up-to-date Cygwin system (not necessarily complete) but that happens to have become unmounted*, and point setup.exe to it, then 2.510.2.2 correctly identifies it, checks that nothing needs updating, and exits after remounting. The more modern exe's when pointed at it nevertheless require a complete download, as though building a fresh installation from scratch. Some part of the "what have we here?" checking procedures that setup pursues seems to have become de-railed with the modern versions. * "Unmounted": not an untypical situation, by accident or by design. An accident could occasionally happen to anyone. For those of us with our Cygwin system on a portable device used with more than one host (eg work/ home/ other) un-mounting then re-mounting by design is the safest way (or not a wrong way) to maintain things in a good state. There are lots of ways to re-mount, and actually I don't usually use setup.exe to achieve re-mounting, but nevertheless it's quite a good way, and should still work? Fergus -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/