Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Sat, 26 May 2001 21:44:17 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: Cygwin Setup 2.54 Message-ID: <20010526214417.A10788@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <990908849.14828.ezmlm@sources.redhat.com> <3B10426C.7080008@gruntose.com> <3B105731.A3E5DAB6@ece.gatech.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <3B105731.A3E5DAB6@ece.gatech.edu>; from cwilson@ece.gatech.edu on Sat, May 26, 2001 at 09:24:02PM -0400 On Sat, May 26, 2001 at 09:24:02PM -0400, Charles S. Wilson wrote: >"Fred T. Hamster" wrote: >> is the official installation process now involving a bunch of registry >> edits before cygwin can be installed again, or is this setup program >> actually quite busted? > >It appears that the new setup program is not operating correctly for >SOME users. This may be because setup itself is broken, or because the >affected users have some wierdness in their local machine. > >In my case, I just used the new setup.exe to update a pre-existing >install (that is, I used it to install the most recent inetutils, >openssh, and python packages -- I already had older versions of those >packages installed). > >It worked flawlessly. Prediction: It will work flawlessly for every person who is remotely capable of debugging it. The problems with weird directories being created sounds a lot like random memory corruption. Wish I could reproduce it. Maybe I should try building it with electric fence or something. cgf -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple