Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Date: Thu, 4 Apr 2002 08:52:21 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: ncftp current release won't run - missing CYGREADLINE5.DLL Message-ID: <20020404135221.GC27509@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <2284-Thu04Apr2002134430+0000-starksb AT ebi DOT ac DOT uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2284-Thu04Apr2002134430+0000-starksb@ebi.ac.uk> User-Agent: Mutt/1.3.23.1i On Thu, Apr 04, 2002 at 01:44:30PM +0000, David Starks-Browning wrote: >On Thursday 4 Apr 02, Robert Collins writes: >> > Sorry, but I ran the newest setup This Week (monday), and it >> > broke my ftpd operation, ("Can't set uid") and tossed out the >> > cygreadline5.dll breaking ncftp.exe so I'm not spreading old >> > information. >> > >> > One of the posters aimed me at the Faq which talks about >> > how dll's can get deleted, and how to manually walk thru >> > the installation and install separate packages in order to >> > restore deleted dlls, >> > which I then paraphrased and posted in reply >> > to Robert Collins question. >> > >> > If setup.exe is now fixed, thats great, >> > I guess the Faq needs to be updated. >> >> Yes, you're right. > >Someone will have to explain to me how the FAQ is wrong here. >(Apologies if it's been stated. This thread has been difficult for me >to follow, even after studying it in the list archives.) The FAQ isn't wrong. The problem can still exist and probably will exist for a couple of months. It's still possible that someone could have a corrupted installation and not notice it. I don't think that setup.exe will notice that you have a missing dll and download it automatically unless the package with the DLL is newer than the installed package. I am concerned by reports that someone updated their installation (apparently) with the most recent setup.exe and still had the problem. If that is the case, then setup.exe isn't really fixed. I think we need more data before we proclaim that setup.exe is fixed but, regardless, the FAQ entry should stay. cgf -- 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/