Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Subject: Re: Slight problem with setup.exe utility From: Robert Collins To: Ronald Landheer Cc: cygwin AT cygwin DOT com In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.13 (Preview Release) Date: 04 Sep 2001 22:45:17 +1000 Message-Id: <999607523.7413.5.camel@lifelesswks> Mime-Version: 1.0 X-OriginalArrivalTime: 04 Sep 2001 12:32:24.0022 (UTC) FILETIME=[A62B5760:01C1353D] On Tue, 2001-09-04 at 22:25, Ronald Landheer wrote: > Hello all, > > I've installed Cygwin quite a while ago, but as I had a severe computer > crash yesterday, I had to re-install both Windows and cygwin from > scratch. I had some old downloads lying around, in which the cygwin > tarball was called cygwin-1.3.2-1.tar.gz while it is now called cygwin- > 1.3.2-1.tar.bz2. I don't know what the reason of the filename change is > - as there is no version change here, but it confuses the setup utility: > it does not say that my cygwin is old, but it refuses to unpack because > the .bz2 file doesn't exist. Huh? Did you use the old setup.exe with the old .ini and old tarballs, or did you use a newer tarball and and old .ini with the old setup.exe? Setup will warn if incompatible options have been introduced, and tar.bz2 handling is built into the current setup.exe available on the website. Sounds like you would have been better off downloading the current setup.exe and running it from your old download directory. That would likely have behaved better. 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/