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 Date: Tue, 29 May 2001 12:22:10 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Cygwin Setup 2.54 Message-ID: <20010529122210.B4844@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <990908849 DOT 14828 DOT ezmlm AT sources DOT redhat DOT com> <3B10426C DOT 7080008 AT gruntose DOT com> <3B105731 DOT A3E5DAB6 AT ece DOT gatech DOT edu> <20010526214417 DOT A10788 AT redhat DOT com> <3B13A8D8 DOT 448BC50B AT yahoo DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <3B13A8D8.448BC50B@yahoo.com>; from earnie_boyd@yahoo.com on Tue, May 29, 2001 at 09:49:12AM -0400 On Tue, May 29, 2001 at 09:49:12AM -0400, Earnie Boyd wrote: >Christopher Faylor wrote: >> >> 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. >> > >Don't you find it strange that the people that are having problems are >the ones that are deleting their previous installation? The workaround >to this problem is don't delete your current installation, just use >setup with the current installation. Possibly, but I tried deleting my current installation and updated with no problem. I did eventually duplicate the problem on another machine. It was due to the use of a freed memory pointer. It should be fixed now, so we can stop talking about this. If it is not fixed, lets start a email thread. This one should be dead already. cgf -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple