Re: Apache HTTP Server 1.3.33-1 release available
On Mar 8 23:59, Robert Richter wrote: Hi all, there is a new release available of Apache HTTP Server 1.3.33. The package is placed here: http://www.fast4ward.de/cygwin/ Please take a look at the README and setup.hint files below. The Apache package contains the mod_ssl EAPI patch but no additional module extensions. These are part of further releases. I am also interested in becoming the package maintainer for Apache 1.3.x. Cool. Can you please send the full URLs to the binary source and setup.hint files to this list? Did you notice that an Apache2 package is coming to speed as well? It would be pretty important that the two packages don't collide. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader mailto:cygwin@cygwin.com Red Hat, Inc.
Re: Apache HTTP Server 1.3.33-1 release available
Corinna Vinschen wrote: On Mar 8 23:59, Robert Richter wrote: Hi all, there is a new release available of Apache HTTP Server 1.3.33. The package is placed here: http://www.fast4ward.de/cygwin/ Please take a look at the README and setup.hint files below. The Apache package contains the mod_ssl EAPI patch but no additional module extensions. These are part of further releases. I am also interested in becoming the package maintainer for Apache 1.3.x. Cool. Can you please send the full URLs to the binary source and setup.hint files to this list? Did you notice that an Apache2 package is coming to speed as well? It would be pretty important that the two packages don't collide. I took care to ensure that my upcoming apache2 packages does not collide with the current apache 1.3 package - unless this new 1.3.x package is more than a simple version upgrade, there should be no problems. Doesn't hurt to check, though. Although, *PLEASE* remove the really pointless sleep commands from the postinstall script, if you haven't done that already. Max.
Re: coreutils-5.3.0-3
I have rechecked some inconsistencies with the magic .exe suffix handling (see http://sourceware.org/bugzilla/show_bug.cgi?id=581) with coreutils 5.3.0 and here is an updated summary of inconsistencies and unexpected behavior (some issues resolved, some new ones appeared): [EMAIL PROTECTED]:~ ls x* x.exe [EMAIL PROTECTED]:~ cat x bash: x: cannot overwrite existing file -- should have created x which does not exist [EMAIL PROTECTED]:~ ls x* x.exe [EMAIL PROTECTED]:~ ln x y -- OK [EMAIL PROTECTED]:~ mv x y /bin/mv: cannot remove `x': No such file or directory -- misleading message [EMAIL PROTECTED]:~ mv -i x.exe y.exe -- should have prompted ls y* y.exe mv y.exe y /bin/mv: `y.exe' and `y' are the same file -- should have renamed [EMAIL PROTECTED]:~ ls x* y* x.exe y [EMAIL PROTECTED]:~ cp -i x y /bin/cp: overwrite `y'? y /bin/cp: cannot create regular file `y.exe': No such file or directory -- confusing message; should have created y [EMAIL PROTECTED]:~ ls x* x.exe [EMAIL PROTECTED]:~ rm -i x /bin/rm: remove regular file `x'? y /bin/rm: cannot remove `x': No such file or directory -- handling inconsistent; first, it maps, then no more [EMAIL PROTECTED]:~ ls x* x.exe [EMAIL PROTECTED]:~ ls -i x 3659174697246106 x -- ^ this is actually x.exe [EMAIL PROTECTED]:~ touch x [EMAIL PROTECTED]:~ ls -i x 1970324836996817 x -- ^ now it's x, a different file -- mapping inconsistent; maybe it should rather look like: [EMAIL PROTECTED]:~ ls x* x.exe [EMAIL PROTECTED]:~ ls x x.exe -- this is my proposal Kind regards, Thomas Wolff
