This is the mail archive of the
mailing list for the Cygwin project.
RE: Bug in setup.exe 126.96.36.199
- From: "Robert Collins" <robert dot collins at itdomain dot com dot au>
- To: <cygwin at cygwin dot com>
- Date: Sun, 21 Apr 2002 16:32:40 +1000
- Subject: RE: Bug in setup.exe 188.8.131.52
> -----Original Message-----
> From: Christopher Faylor [mailto:firstname.lastname@example.org]
> Sent: Saturday, April 20, 2002 10:16 AM
> To: email@example.com
> Subject: Re: Bug in setup.exe 184.108.40.206
> On Sat, Apr 20, 2002 at 09:31:02AM +1000, Robert Collins wrote:
> >> -----Original Message-----
> >> From: Cliff Hones [mailto:firstname.lastname@example.org]
> >> 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
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..
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html