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 content-class: urn:content-classes:message Subject: RE: Bug in setup.exe 2.194.2.24 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sun, 21 Apr 2002 16:32:40 +1000 X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Robert Collins" To: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g3L6WuP29744 > -----Original Message----- > From: Christopher Faylor [mailto:cgf AT redhat DOT com] > Sent: Saturday, April 20, 2002 10:16 AM > To: cygwin AT cygwin DOT com > Subject: Re: Bug in setup.exe 2.194.2.24 > > > On Sat, Apr 20, 2002 at 09:31:02AM +1000, Robert Collins wrote: > > > > > >> -----Original Message----- > >> From: Cliff Hones [mailto:cliff AT aonix DOT co DOT uk] > >> Sent: Saturday, April 20, 2002 9:10 AM > > > >> Since noone acknowledged it was a bug I've been assuming it was a > >(rather strange to me) design feature. > > > >Actually, I acknowledged it as a bug, but one I couldn't > repeat until I > >was given an exact recipe on cygwin-apps. I've jet to track > it down and > >squash it though. And I *stil* cannot reproduce it. Setup detects the local files *every single time*. The only thing I can think of is platform: Can anyone reproduce the bug on windows XP? If so, please please please tell me how. Otherwise, I'll forge on ahead with getting a new HEAD tidyup done, including the URL class that Pavel worked quite hard on, that will allow some normalisations - and may be able to fix the bug. (The only thing I can see that might cause it is that the file paths look like d:\foo\bar/release/package/packagefile, which could potentially confuse the MSVCRT library.. 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/