X-Spam-Check-By: sourceware.org Date: Tue, 21 Aug 2007 15:26:54 +0200 From: Angelo Graziosi To: cygwin AT cygwin DOT com Subject: A problem with setup.exe (?) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 I have observed this problem with setup.exe 2.575, 2.573.2.2 and 2.578 (but, perhaps it is not a stricly setup problem). Usually when one has some experimental package installed, setup, while installing some other package, tries to reinstall the 'Cur' package. So one should click to keep the exp. package. And this is OK. This morning I forgot this and setup started to reinstall the cur. version of libtool package. When I see this I clicked the 'Cancel' button to break the reinstall. This has caused a corrupted lst.gz file (libtool1.5.lst.gz): trying to gunzip manually: unexpected end of file When I have tried to reinstall the package (to be sure that all was OK), choosing 'Reinstall', there was the error window: An error occured in setup-2.573.2.2.... Falag the error to Microsoft.. ... Yes/NO ... and setup hanged. After many tries, the solution has been to remove the corrupted lst.gz file and then reinstalling. So the question is: Should setup give a warning that the lst.gz file was corrupted, suggesting to remove it? But perhaps, the simplest solution should be to remove the 'Cancel' button from setup... Cheers, Angelo. -- 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/