You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Jim Jagielski <ji...@jaguNET.com> on 2008/06/11 02:50:50 UTC
[VOTE] Release Apache HTTP Server 2.2.9
Test tarballs for Apache httpd 2.2.9 are available at:
http://httpd.apache.org/dev/dist/
Your votes please;
+/-1
[ ] Release httpd-2.2.9 as GA
----
DO NOT begin distributing these in any manner whatsoever, please note
that
you can seriously mess up any user who installs these packages if they
are
ultimately rejected.
Re: [VOTE] Release Apache HTTP Server 2.2.9
Posted by Steffen <in...@apachelounge.com>.
Builds fine on Windows and successfully installed and tested.
Runs with all popular modules, except mod_fcgid needed a patch (see post
from Tom). After ASF releases 2.2.9 we make a mod-fcgid for 2.2.9 available.
Steffen
----- Original Message -----
From: "Jim Jagielski" <ji...@jaguNET.com>
To: <de...@httpd.apache.org>
Cc: <te...@httpd.apache.org>
Sent: Wednesday, 11 June, 2008 02:50
Subject: [VOTE] Release Apache HTTP Server 2.2.9
> Test tarballs for Apache httpd 2.2.9 are available at:
>
> http://httpd.apache.org/dev/dist/
>
> Your votes please;
>
> +/-1
> [ ] Release httpd-2.2.9 as GA
>
> ----
>
> DO NOT begin distributing these in any manner whatsoever, please note
> that
> you can seriously mess up any user who installs these packages if they
> are
> ultimately rejected.
>
Re: [VOTE] Release Apache HTTP Server 2.2.9
Posted by jean-frederic clere <jf...@gmail.com>.
Jim Jagielski wrote:
> Test tarballs for Apache httpd 2.2.9 are available at:
>
> http://httpd.apache.org/dev/dist/
>
> Your votes please;
>
> +/-1
> [ ] Release httpd-2.2.9 as GA
>
> ----
>
> DO NOT begin distributing these in any manner whatsoever, please note that
> you can seriously mess up any user who installs these packages if they are
> ultimately rejected.
>
On HP-UX (HP-UX dev25 B.11.23 U ia64) I have:
+++
mkdir /home/jfclere/APACHE9_ia64_HP-UX/lib/apr-util-1
sh: Syntax error at line 1 : `;' is not expected.
*** Error exit code 2
Stop.
*** Error exit code 1
Stop.
*** Error exit code 1
Stop.
+++
It is fixed by r663499 in apr-util trunk.
Otherwise It looks ok on other machines where I built it.
HP-UX and Solaris.
Cheers
Jean-Frederic
Re: [VOTE] Release Apache HTTP Server 2.2.9
Posted by Jim Jagielski <ji...@jaguNET.com>.
On Jun 12, 2008, at 12:41 PM, William A. Rowe, Jr. wrote:
>
> We would also place this .patch in patches/apply-to-2.2.9/ for
> clarity.
>
+1
Re: [VOTE] Release Apache HTTP Server 2.2.9
Posted by "William A. Rowe, Jr." <wr...@rowe-clan.net>.
Tom Donovan wrote:
>
> FYI - the MySQL driver seems to build OK if it is linked with
> libmysql.lib instead of
> mysqlclient.lib.
Feel free to update over on apr-util trunk and 1.3 branch. We can't
suggest it for 1.3.0 since the 'long long' construct broke the compile,
but it will be nice to let it work as of apr 1.3.1.
Bill
Re: [VOTE] Release Apache HTTP Server 2.2.9
Posted by Tom Donovan <do...@bellatlantic.net>.
William A. Rowe, Jr. wrote:
> William A. Rowe, Jr. wrote:
>>
>> The two files below are part of the httpd-2.2.9-win32-src.zip file
>> package,
>> which has been uploaded to httpd.apache.org/dev/dist/ (and should show up
>> sometime shortly when the server syncs). The README-win32.txt will also
>> be added to the binary distribution (msi) for dbd driver instructions.
>>
>> We would also place this .patch in patches/apply-to-2.2.9/ for clarity.
>
> Actually the patch is even simpler, my mistake (I discovered that the extra
> changes to apr.hw are simply unnecessary).
>
> Final proposed patch attached.
Looks good. I'll give it a test when it shows up on /dev/dist
FYI - the MySQL driver seems to build OK if it is linked with libmysql.lib instead of
mysqlclient.lib.
libmysql.lib is usually in {mysql}\lib\opt on Windows.
It needs {mysql}\bin\libmysql.dll at runtime.
-tom-
Re: [VOTE] Release Apache HTTP Server 2.2.9
Posted by "William A. Rowe, Jr." <wr...@rowe-clan.net>.
William A. Rowe, Jr. wrote:
>
> The two files below are part of the httpd-2.2.9-win32-src.zip file package,
> which has been uploaded to httpd.apache.org/dev/dist/ (and should show up
> sometime shortly when the server syncs). The README-win32.txt will also
> be added to the binary distribution (msi) for dbd driver instructions.
>
> We would also place this .patch in patches/apply-to-2.2.9/ for clarity.
Actually the patch is even simpler, my mistake (I discovered that the extra
changes to apr.hw are simply unnecessary).
Final proposed patch attached.
Re: [VOTE] Release Apache HTTP Server 2.2.9
Posted by "William A. Rowe, Jr." <wr...@rowe-clan.net>.
Tom Donovan wrote:
> APR 1.3 will require a code change in Windows modules which launch
> FastCGI programs using apr_proc_create. They will need to use the new
> APR_NO_FILE attribute. This doesn't affect any other platforms AFAIK.
The trouble is that there are other side effects of using apr-1.2, but if
needed it does exist at http://www.apache.org/dist/apr/binaries/win32/.
Here's my proposed solution to Makefile.win changes that Tom and I have
both observed (not affecting sln/dsp builds, but affecting mak file builds),
plus the problem with apr.hw's invalid default of IPV6 true, and additional
commentary about the binary connectors.
The two files below are part of the httpd-2.2.9-win32-src.zip file package,
which has been uploaded to httpd.apache.org/dev/dist/ (and should show up
sometime shortly when the server syncs). The README-win32.txt will also
be added to the binary distribution (msi) for dbd driver instructions.
We would also place this .patch in patches/apply-to-2.2.9/ for clarity.
Objections or other feedback?
Bill
Re: [VOTE] Release Apache HTTP Server 2.2.9
Posted by Tom Donovan <do...@bellatlantic.net>.
APR 1.3 will require a code change in Windows modules which launch FastCGI programs using
apr_proc_create. They will need to use the new APR_NO_FILE attribute. This doesn't affect any
other platforms AFAIK.
e.g.
apr_procattr_io_set(attr, NULL, APR_NO_FILE, APR_NO_FILE);
This was pretty well discussed last September per bug 43329, so hopefully most module authors
(mod_fastcgi, mod_fcgid, etc.) have prepared for it. There's always the option of falling back to
APR 1.2 for anyone who cannot get an updated Windows FastCGI module, so this shouldn't be too big a
problem.
Back in September we didn't expect APR 1.3 until Apache 2.4, so we may want to call some attention
to this when the Windows 2.2.9 binaries get released. Maybe even offer an optional APR 1.2 download
to let users fall back easily, since most Windows users don't build Apache from source.
-tom-
Jim Jagielski wrote:
> Test tarballs for Apache httpd 2.2.9 are available at:
>
> http://httpd.apache.org/dev/dist/
>
Re: showstopper to 1.3.1?
Posted by Plüm,
Rüdiger,
VF-Group <ru...@vodafone.com>.
> -----Ursprüngliche Nachricht-----
> Von: Joe Orton
> Gesendet: Mittwoch, 18. Juni 2008 17:20
> An: Ruediger Pluem
> Cc: APR Developer List; dev@httpd.apache.org
> Betreff: Re: showstopper to 1.3.1?
>
> On Sat, Jun 14, 2008 at 11:24:43PM +0200, Ruediger Pluem wrote:
> > So the code before said that if port_getn returns -1 (==
> fails) we return APR_TIMEUP
> > if the error is ETIME or EINTR and APR_EGENERAL.
> > So IMHO the error message (in this IMHO the same) would
> have been shown with the old
> > code.
> > What is more strange to me is that we get a timeout error
> ((70007)The timeout specified has
> > expired: apr_pollset_poll:) even thought we called
> apr_pollset_poll with -1 as timeout which
> > means wait indefinitely or no timeout. The implementation
> of apr_pollset_poll seems to be
> > correct as it ensures that we supply NULL in this case to
> port_getn. But OTOH the man page
> > for port_get / port_getn documents timeout behaviour only
> for port_get (setting timeout parameter
> > to null means not timeout) not for port_getn. So couldn't
> this be a Solaris bug?
>
> It may be working as designed - this code path gets trigged
> when all the
> fds in the pollset get closed asynchronously; see PR 42829 and the
> thread concerning that bug on this list.
So do I get it correct that port_getn if called only with closed
fd's associated to this port returns immediately with ETIME set as
errno despite its timeout being set to infinite?
>
> If it is working as designed it is arguably more useful than
> the epoll
> behaviour in the same case; at least, it's more useful for httpd.
> AFAICT the only effect of this to prefork is to generate some
> error_log
> spam; could be ignored easily enough.
>
> The APR change r641661 certainly looks correct anyway.
As I understand it an error would be returned by apr_pollset_poll
with and without r641661 in place.
Regards
Rüdiger
Re: showstopper to 1.3.1?
Posted by Plüm,
Rüdiger,
VF-Group <ru...@vodafone.com>.
> -----Ursprüngliche Nachricht-----
> Von: Joe Orton
> Gesendet: Mittwoch, 18. Juni 2008 17:20
> An: Ruediger Pluem
> Cc: APR Developer List; dev@httpd.apache.org
> Betreff: Re: showstopper to 1.3.1?
>
> On Sat, Jun 14, 2008 at 11:24:43PM +0200, Ruediger Pluem wrote:
> > So the code before said that if port_getn returns -1 (==
> fails) we return APR_TIMEUP
> > if the error is ETIME or EINTR and APR_EGENERAL.
> > So IMHO the error message (in this IMHO the same) would
> have been shown with the old
> > code.
> > What is more strange to me is that we get a timeout error
> ((70007)The timeout specified has
> > expired: apr_pollset_poll:) even thought we called
> apr_pollset_poll with -1 as timeout which
> > means wait indefinitely or no timeout. The implementation
> of apr_pollset_poll seems to be
> > correct as it ensures that we supply NULL in this case to
> port_getn. But OTOH the man page
> > for port_get / port_getn documents timeout behaviour only
> for port_get (setting timeout parameter
> > to null means not timeout) not for port_getn. So couldn't
> this be a Solaris bug?
>
> It may be working as designed - this code path gets trigged
> when all the
> fds in the pollset get closed asynchronously; see PR 42829 and the
> thread concerning that bug on this list.
So do I get it correct that port_getn if called only with closed
fd's associated to this port returns immediately with ETIME set as
errno despite its timeout being set to infinite?
>
> If it is working as designed it is arguably more useful than
> the epoll
> behaviour in the same case; at least, it's more useful for httpd.
> AFAICT the only effect of this to prefork is to generate some
> error_log
> spam; could be ignored easily enough.
>
> The APR change r641661 certainly looks correct anyway.
As I understand it an error would be returned by apr_pollset_poll
with and without r641661 in place.
Regards
Rüdiger
Re: showstopper to 1.3.1?
Posted by Joe Orton <jo...@redhat.com>.
On Sat, Jun 14, 2008 at 11:24:43PM +0200, Ruediger Pluem wrote:
> So the code before said that if port_getn returns -1 (== fails) we return APR_TIMEUP
> if the error is ETIME or EINTR and APR_EGENERAL.
> So IMHO the error message (in this IMHO the same) would have been shown with the old
> code.
> What is more strange to me is that we get a timeout error ((70007)The timeout specified has
> expired: apr_pollset_poll:) even thought we called apr_pollset_poll with -1 as timeout which
> means wait indefinitely or no timeout. The implementation of apr_pollset_poll seems to be
> correct as it ensures that we supply NULL in this case to port_getn. But OTOH the man page
> for port_get / port_getn documents timeout behaviour only for port_get (setting timeout parameter
> to null means not timeout) not for port_getn. So couldn't this be a Solaris bug?
It may be working as designed - this code path gets trigged when all the
fds in the pollset get closed asynchronously; see PR 42829 and the
thread concerning that bug on this list.
If it is working as designed it is arguably more useful than the epoll
behaviour in the same case; at least, it's more useful for httpd.
AFAICT the only effect of this to prefork is to generate some error_log
spam; could be ignored easily enough.
The APR change r641661 certainly looks correct anyway.
joe
Re: showstopper to 1.3.1?
Posted by Joe Orton <jo...@redhat.com>.
On Sat, Jun 14, 2008 at 11:24:43PM +0200, Ruediger Pluem wrote:
> So the code before said that if port_getn returns -1 (== fails) we return APR_TIMEUP
> if the error is ETIME or EINTR and APR_EGENERAL.
> So IMHO the error message (in this IMHO the same) would have been shown with the old
> code.
> What is more strange to me is that we get a timeout error ((70007)The timeout specified has
> expired: apr_pollset_poll:) even thought we called apr_pollset_poll with -1 as timeout which
> means wait indefinitely or no timeout. The implementation of apr_pollset_poll seems to be
> correct as it ensures that we supply NULL in this case to port_getn. But OTOH the man page
> for port_get / port_getn documents timeout behaviour only for port_get (setting timeout parameter
> to null means not timeout) not for port_getn. So couldn't this be a Solaris bug?
It may be working as designed - this code path gets trigged when all the
fds in the pollset get closed asynchronously; see PR 42829 and the
thread concerning that bug on this list.
If it is working as designed it is arguably more useful than the epoll
behaviour in the same case; at least, it's more useful for httpd.
AFAICT the only effect of this to prefork is to generate some error_log
spam; could be ignored easily enough.
The APR change r641661 certainly looks correct anyway.
joe
Re: showstopper to 1.3.1?
Posted by Ruediger Pluem <rp...@apache.org>.
On 06/14/2008 10:42 PM, William A. Rowe, Jr. wrote:
> Guys, if anyone is looking at this, I'll hold off from tagging a bit
> longer,
> as I'd rather have apr-1.3.1 address all the platform quirks we identified
> in preparing 2.2.9 for release. But if I hear nothing, I'll have to
> just move ahead :)
>
> Bill
>
> Paul Querna wrote:
>>
>> On aurora.apache.org, shortly after installing the new version, we hit
>> a problem with apr_pollset_poll:
>>
>> [Thu Jun 12 05:36:51 2008] [error] (70007)The timeout specified has
>> expired: apr_pollset_poll: (listen)
>> [Thu Jun 12 05:36:52 2008] [notice] caught SIGTERM, shutting down
>>
>> If you look in worker.c, around line 687, you can see that if do a
>> graceful shutdown if we get an unexpected error from apr_pollset_poll.
>>
>> This appears to be a regression caused by r641661:
>> https://svn.apache.org/viewvc?view=rev&revision=641661
>>
>> Which was a fix for PR 42580:
>> https://issues.apache.org/bugzilla/show_bug.cgi?id=42580
>>
>> This appears to be an relative edge case on Solaris 10 -- it hasn't
>> happened again, and it is a regression in APR, but relatively small,
>> so I am still +1 for httpd-2.2.9 shipping.
Is this really a regression in APR or were we just as lucky before as we
were after?
Code from httpd
rv = apr_pollset_poll(pollset, -1, &numdesc, &pdesc);
if (rv != APR_SUCCESS) {
if (APR_STATUS_IS_EINTR(rv)) {
continue;
}
/* apr_pollset_poll() will only return errors in catastrophic
* circumstances. Let's try exiting gracefully, for now. */
ap_log_error(APLOG_MARK, APLOG_ERR, rv,
(const server_rec *) ap_server_conf,
"apr_pollset_poll: (listen)");
So we the error message logged if apr_pollset_poll returns anything different then
APR_SUCCESS or APR_EINTR.
So lets have a look at r641661:
--- apr/apr/trunk/poll/unix/port.c 2008/03/27 00:31:21 641660
+++ apr/apr/trunk/poll/unix/port.c 2008/03/27 00:46:05 641661
@@ -295,12 +295,7 @@
if (ret == -1) {
(*num) = 0;
- if (errno == ETIME || errno == EINTR) {
- rv = APR_TIMEUP;
- }
- else {
- rv = APR_EGENERAL;
- }
+ rv = apr_get_netos_error();
}
else if (nget == 0) {
rv = APR_TIMEUP;
So the code before said that if port_getn returns -1 (== fails) we return APR_TIMEUP
if the error is ETIME or EINTR and APR_EGENERAL.
So IMHO the error message (in this IMHO the same) would have been shown with the old
code.
What is more strange to me is that we get a timeout error ((70007)The timeout specified has
expired: apr_pollset_poll:) even thought we called apr_pollset_poll with -1 as timeout which
means wait indefinitely or no timeout. The implementation of apr_pollset_poll seems to be
correct as it ensures that we supply NULL in this case to port_getn. But OTOH the man page
for port_get / port_getn documents timeout behaviour only for port_get (setting timeout parameter
to null means not timeout) not for port_getn. So couldn't this be a Solaris bug?
Regards
Rüdiger
Re: showstopper to 1.3.1?
Posted by Ruediger Pluem <rp...@apache.org>.
On 06/14/2008 10:42 PM, William A. Rowe, Jr. wrote:
> Guys, if anyone is looking at this, I'll hold off from tagging a bit
> longer,
> as I'd rather have apr-1.3.1 address all the platform quirks we identified
> in preparing 2.2.9 for release. But if I hear nothing, I'll have to
> just move ahead :)
>
> Bill
>
> Paul Querna wrote:
>>
>> On aurora.apache.org, shortly after installing the new version, we hit
>> a problem with apr_pollset_poll:
>>
>> [Thu Jun 12 05:36:51 2008] [error] (70007)The timeout specified has
>> expired: apr_pollset_poll: (listen)
>> [Thu Jun 12 05:36:52 2008] [notice] caught SIGTERM, shutting down
>>
>> If you look in worker.c, around line 687, you can see that if do a
>> graceful shutdown if we get an unexpected error from apr_pollset_poll.
>>
>> This appears to be a regression caused by r641661:
>> https://svn.apache.org/viewvc?view=rev&revision=641661
>>
>> Which was a fix for PR 42580:
>> https://issues.apache.org/bugzilla/show_bug.cgi?id=42580
>>
>> This appears to be an relative edge case on Solaris 10 -- it hasn't
>> happened again, and it is a regression in APR, but relatively small,
>> so I am still +1 for httpd-2.2.9 shipping.
Is this really a regression in APR or were we just as lucky before as we
were after?
Code from httpd
rv = apr_pollset_poll(pollset, -1, &numdesc, &pdesc);
if (rv != APR_SUCCESS) {
if (APR_STATUS_IS_EINTR(rv)) {
continue;
}
/* apr_pollset_poll() will only return errors in catastrophic
* circumstances. Let's try exiting gracefully, for now. */
ap_log_error(APLOG_MARK, APLOG_ERR, rv,
(const server_rec *) ap_server_conf,
"apr_pollset_poll: (listen)");
So we the error message logged if apr_pollset_poll returns anything different then
APR_SUCCESS or APR_EINTR.
So lets have a look at r641661:
--- apr/apr/trunk/poll/unix/port.c 2008/03/27 00:31:21 641660
+++ apr/apr/trunk/poll/unix/port.c 2008/03/27 00:46:05 641661
@@ -295,12 +295,7 @@
if (ret == -1) {
(*num) = 0;
- if (errno == ETIME || errno == EINTR) {
- rv = APR_TIMEUP;
- }
- else {
- rv = APR_EGENERAL;
- }
+ rv = apr_get_netos_error();
}
else if (nget == 0) {
rv = APR_TIMEUP;
So the code before said that if port_getn returns -1 (== fails) we return APR_TIMEUP
if the error is ETIME or EINTR and APR_EGENERAL.
So IMHO the error message (in this IMHO the same) would have been shown with the old
code.
What is more strange to me is that we get a timeout error ((70007)The timeout specified has
expired: apr_pollset_poll:) even thought we called apr_pollset_poll with -1 as timeout which
means wait indefinitely or no timeout. The implementation of apr_pollset_poll seems to be
correct as it ensures that we supply NULL in this case to port_getn. But OTOH the man page
for port_get / port_getn documents timeout behaviour only for port_get (setting timeout parameter
to null means not timeout) not for port_getn. So couldn't this be a Solaris bug?
Regards
Rüdiger
Re: showstopper to 1.3.1?
Posted by Oden Eriksson <oe...@mandriva.com>.
Den Monday 16 June 2008 15:23:34 skrev Oden Eriksson:
> Den Saturday 14 June 2008 22:42:03 skrev William A. Rowe, Jr.:
> > Guys, if anyone is looking at this, I'll hold off from tagging a bit
> > longer, as I'd rather have apr-1.3.1 address all the platform quirks we
> > identified in preparing 2.2.9 for release. But if I hear nothing, I'll
> > have to just move ahead :)
> >
> > Bill
>
> I think this was forgotten in apr-util-1.3.0:
>
> --- Makefile.in 2008-05-22 18:37:47.000000000 -0400
> +++ Makefile.in.oden 2008-06-16 07:40:20.000000000 -0400
> @@ -36,6 +36,7 @@
> LDADD_dbd_sqlite3 = @LDADD_dbd_sqlite3@
> LDADD_dbd_mysql = @LDADD_dbd_mysql@
> LDADD_ldap = @LDADD_ldap@
> +LDADD_dbd_freetds = @LDADD_dbd_freetds@
>
> TARGETS = $(TARGET_LIB) aprutil.exp apu-config.out $(APU_MODULES)
>
>
>
> Though it doesn't help much for me on cooker, don't know why it won't link
> correctly. I'm using the latest freetds (0.82).
The freetds stuff from HEAD works.
Re: showstopper to 1.3.1?
Posted by "William A. Rowe, Jr." <wr...@rowe-clan.net>.
Oden Eriksson wrote:
> Den Monday 16 June 2008 18:15:24 skrev William A. Rowe, Jr.:
>> Unclear what was up with your change;
>>
>> --- apr-util-1.3.0/dbd/apr_dbd_freetds.c 2008-05-30 16:45:51.000000000
>> -0400 +++ apr-util-1.3.0.oden/dbd/apr_dbd_freetds.c 2008-06-16
>> 10:08:05.000000000 -0400
>>
>> which isn't on trunk, and since there's no explanation I'm ignoring it as
>> I move forward to deal with any 1.3.2, but you might like to take that up
>> to the apr, or remind us if you had earlier submitted a patch. About the
>> other files touched in your patch, those were all in the 1.3.1 candidate
>> tarball.
>
> I am sorry but I do not touch the development branch very often, the last time
> was about three years ago (like).
Oh no - no hassle, just wondering where the patch came from if not on
development, looking forward to your comments on dev@apr. Thanks again.
Re: showstopper to 1.3.1?
Posted by Oden Eriksson <oe...@mandriva.com>.
Den Monday 16 June 2008 18:15:24 skrev William A. Rowe, Jr.:
> Oden Eriksson wrote:
> > For completeness, this is the patch i had to use for freetds:
> >
> > http://svn.mandriva.com/cgi-bin/viewvc.cgi/packages/cooker/apr-util/curre
> >nt/SOURCES/apr-util-freetds_fix.diff?revision=219531&view=markup Well...
> > Not so important anyway.
>
> Unclear what was up with your change;
>
> --- apr-util-1.3.0/dbd/apr_dbd_freetds.c 2008-05-30 16:45:51.000000000
> -0400 +++ apr-util-1.3.0.oden/dbd/apr_dbd_freetds.c 2008-06-16
> 10:08:05.000000000 -0400
>
> which isn't on trunk, and since there's no explanation I'm ignoring it as
> I move forward to deal with any 1.3.2, but you might like to take that up
> to the apr, or remind us if you had earlier submitted a patch. About the
> other files touched in your patch, those were all in the 1.3.1 candidate
> tarball.
I am sorry but I do not touch the development branch very often, the last time
was about three years ago (like).
> > Additionally I tried to add the odbc stuff as well from HEAD but failed.
>
> FYI There is a list for apr development at dev@apr.apache.org where such
> posts might get more relevant attention, and there are a number of threads
> about a 1.3.1 potential release (soon to be 1.3.2 potential release). You
> might be interested and would be welcomed to join the dialog there.
OK. Thanks. I will try to address these things there instead.
> What are you calling HEAD? repos/asf/apr/apr-util/trunk/? From when?
> Reports were that it should now be ok, you might retry, or better yet point
> out what failed? I know the devs are excited to ship odbc support, and
> would like it to be golden in the first apr-util-1 release.
Yes i meant repos/asf/apr/apr-util/trunk/ it was taken today, but as you said
earlier i have to adress the apr development list.
Cheers.
Re: showstopper to 1.3.1?
Posted by "William A. Rowe, Jr." <wr...@rowe-clan.net>.
Oden Eriksson wrote:
>
> For completeness, this is the patch i had to use for freetds:
>
> http://svn.mandriva.com/cgi-bin/viewvc.cgi/packages/cooker/apr-util/current/SOURCES/apr-util-freetds_fix.diff?revision=219531&view=markup
> Well... Not so important anyway.
Unclear what was up with your change;
--- apr-util-1.3.0/dbd/apr_dbd_freetds.c 2008-05-30 16:45:51.000000000 -0400
+++ apr-util-1.3.0.oden/dbd/apr_dbd_freetds.c 2008-06-16 10:08:05.000000000
-0400
which isn't on trunk, and since there's no explanation I'm ignoring it as
I move forward to deal with any 1.3.2, but you might like to take that up
to the apr, or remind us if you had earlier submitted a patch. About the
other files touched in your patch, those were all in the 1.3.1 candidate
tarball.
> Additionally I tried to add the odbc stuff as well from HEAD but failed.
FYI There is a list for apr development at dev@apr.apache.org where such
posts might get more relevant attention, and there are a number of threads
about a 1.3.1 potential release (soon to be 1.3.2 potential release). You
might be interested and would be welcomed to join the dialog there.
What are you calling HEAD? repos/asf/apr/apr-util/trunk/? From when?
Reports were that it should now be ok, you might retry, or better yet point
out what failed? I know the devs are excited to ship odbc support, and
would like it to be golden in the first apr-util-1 release.
Re: showstopper to 1.3.1?
Posted by Oden Eriksson <oe...@mandriva.com>.
Den Monday 16 June 2008 17:14:18 skrev William A. Rowe, Jr.:
> Oden Eriksson wrote:
> > I think this was forgotten in apr-util-1.3.0:
> >
> > --- Makefile.in 2008-05-22 18:37:47.000000000 -0400
> > +++ Makefile.in.oden 2008-06-16 07:40:20.000000000 -0400
> > +LDADD_dbd_freetds = @LDADD_dbd_freetds@
>
> Already leading off this list of
>
> http://apr.apache.org/dev/dist/CHANGES-APR-UTIL-1.3
>
> >Changes with APR-util 1.3.1
> >
> > *) Add ODBC DBD Driver. [Tom Donovan]
> >
> > *) Fix build of the FreeTDS and MySQL drivers. [Bojan Smojver]
>
> looks like 1.3.1 util may be scuttled for 1.3.2, but it will be available
> sometime rsn.
For completeness, this is the patch i had to use for freetds:
http://svn.mandriva.com/cgi-bin/viewvc.cgi/packages/cooker/apr-util/current/SOURCES/apr-util-freetds_fix.diff?revision=219531&view=markup
Additionally I tried to add the odbc stuff as well from HEAD but failed.
Well... Not so important anyway.
Re: showstopper to 1.3.1?
Posted by "William A. Rowe, Jr." <wr...@rowe-clan.net>.
Oden Eriksson wrote:
>
> I think this was forgotten in apr-util-1.3.0:
>
> --- Makefile.in 2008-05-22 18:37:47.000000000 -0400
> +++ Makefile.in.oden 2008-06-16 07:40:20.000000000 -0400
> +LDADD_dbd_freetds = @LDADD_dbd_freetds@
Already leading off this list of
http://apr.apache.org/dev/dist/CHANGES-APR-UTIL-1.3
>Changes with APR-util 1.3.1
>
> *) Add ODBC DBD Driver. [Tom Donovan]
>
> *) Fix build of the FreeTDS and MySQL drivers. [Bojan Smojver]
looks like 1.3.1 util may be scuttled for 1.3.2, but it will be available
sometime rsn.
Re: showstopper to 1.3.1?
Posted by Oden Eriksson <oe...@mandriva.com>.
Den Saturday 14 June 2008 22:42:03 skrev William A. Rowe, Jr.:
> Guys, if anyone is looking at this, I'll hold off from tagging a bit
> longer, as I'd rather have apr-1.3.1 address all the platform quirks we
> identified in preparing 2.2.9 for release. But if I hear nothing, I'll
> have to just move ahead :)
>
> Bill
I think this was forgotten in apr-util-1.3.0:
--- Makefile.in 2008-05-22 18:37:47.000000000 -0400
+++ Makefile.in.oden 2008-06-16 07:40:20.000000000 -0400
@@ -36,6 +36,7 @@
LDADD_dbd_sqlite3 = @LDADD_dbd_sqlite3@
LDADD_dbd_mysql = @LDADD_dbd_mysql@
LDADD_ldap = @LDADD_ldap@
+LDADD_dbd_freetds = @LDADD_dbd_freetds@
TARGETS = $(TARGET_LIB) aprutil.exp apu-config.out $(APU_MODULES)
Though it doesn't help much for me on cooker, don't know why it won't link
correctly. I'm using the latest freetds (0.82).
showstopper to 1.3.1?
Posted by "William A. Rowe, Jr." <wr...@rowe-clan.net>.
Guys, if anyone is looking at this, I'll hold off from tagging a bit longer,
as I'd rather have apr-1.3.1 address all the platform quirks we identified
in preparing 2.2.9 for release. But if I hear nothing, I'll have to just
move ahead :)
Bill
Paul Querna wrote:
>
> On aurora.apache.org, shortly after installing the new version, we hit a
> problem with apr_pollset_poll:
>
> [Thu Jun 12 05:36:51 2008] [error] (70007)The timeout specified has
> expired: apr_pollset_poll: (listen)
> [Thu Jun 12 05:36:52 2008] [notice] caught SIGTERM, shutting down
>
> If you look in worker.c, around line 687, you can see that if do a
> graceful shutdown if we get an unexpected error from apr_pollset_poll.
>
> This appears to be a regression caused by r641661:
> https://svn.apache.org/viewvc?view=rev&revision=641661
>
> Which was a fix for PR 42580:
> https://issues.apache.org/bugzilla/show_bug.cgi?id=42580
>
> This appears to be an relative edge case on Solaris 10 -- it hasn't
> happened again, and it is a regression in APR, but relatively small, so
> I am still +1 for httpd-2.2.9 shipping.
showstopper to 1.3.1?
Posted by "William A. Rowe, Jr." <wr...@rowe-clan.net>.
Guys, if anyone is looking at this, I'll hold off from tagging a bit longer,
as I'd rather have apr-1.3.1 address all the platform quirks we identified
in preparing 2.2.9 for release. But if I hear nothing, I'll have to just
move ahead :)
Bill
Paul Querna wrote:
>
> On aurora.apache.org, shortly after installing the new version, we hit a
> problem with apr_pollset_poll:
>
> [Thu Jun 12 05:36:51 2008] [error] (70007)The timeout specified has
> expired: apr_pollset_poll: (listen)
> [Thu Jun 12 05:36:52 2008] [notice] caught SIGTERM, shutting down
>
> If you look in worker.c, around line 687, you can see that if do a
> graceful shutdown if we get an unexpected error from apr_pollset_poll.
>
> This appears to be a regression caused by r641661:
> https://svn.apache.org/viewvc?view=rev&revision=641661
>
> Which was a fix for PR 42580:
> https://issues.apache.org/bugzilla/show_bug.cgi?id=42580
>
> This appears to be an relative edge case on Solaris 10 -- it hasn't
> happened again, and it is a regression in APR, but relatively small, so
> I am still +1 for httpd-2.2.9 shipping.
showstopper to 1.3.1?
Posted by "William A. Rowe, Jr." <wr...@rowe-clan.net>.
Guys, if anyone is looking at this, I'll hold off from tagging a bit longer,
as I'd rather have apr-1.3.1 address all the platform quirks we identified
in preparing 2.2.9 for release. But if I hear nothing, I'll have to just
move ahead :)
Bill
Paul Querna wrote:
>
> On aurora.apache.org, shortly after installing the new version, we hit a
> problem with apr_pollset_poll:
>
> [Thu Jun 12 05:36:51 2008] [error] (70007)The timeout specified has
> expired: apr_pollset_poll: (listen)
> [Thu Jun 12 05:36:52 2008] [notice] caught SIGTERM, shutting down
>
> If you look in worker.c, around line 687, you can see that if do a
> graceful shutdown if we get an unexpected error from apr_pollset_poll.
>
> This appears to be a regression caused by r641661:
> https://svn.apache.org/viewvc?view=rev&revision=641661
>
> Which was a fix for PR 42580:
> https://issues.apache.org/bugzilla/show_bug.cgi?id=42580
>
> This appears to be an relative edge case on Solaris 10 -- it hasn't
> happened again, and it is a regression in APR, but relatively small, so
> I am still +1 for httpd-2.2.9 shipping.
---------------------------------------------------------------------
To unsubscribe, e-mail: testers-unsubscribe@httpd.apache.org
For additional commands, e-mail: testers-help@httpd.apache.org
Re: [VOTE] Release Apache HTTP Server 2.2.9
Posted by Paul Querna <ch...@force-elite.com>.
Jim Jagielski wrote:
> Test tarballs for Apache httpd 2.2.9 are available at:
>
> http://httpd.apache.org/dev/dist/
>
> Your votes please;
>
> +/-1
> [+1] Release httpd-2.2.9 as GA
+1 from me.
Upgraded {eos,aurora}.apache.org to 2.2.9 w/ the bundled APR:
http://eos.apache.org/server-status
http://aurora.apache.org/server-status
Both are Solaris 10/sparc.
These machines host www.apache.org and $tlp.apache.org.
Please let infrastructure know if you see any problems.
During the upgrade, it appears we hit one regression in APR 1.3.0.
On aurora.apache.org, shortly after installing the new version, we hit a
problem with apr_pollset_poll:
[Thu Jun 12 05:36:51 2008] [error] (70007)The timeout specified has
expired: apr_pollset_poll: (listen)
[Thu Jun 12 05:36:52 2008] [notice] caught SIGTERM, shutting down
If you look in worker.c, around line 687, you can see that if do a
graceful shutdown if we get an unexpected error from apr_pollset_poll.
This appears to be a regression caused by r641661:
https://svn.apache.org/viewvc?view=rev&revision=641661
Which was a fix for PR 42580:
https://issues.apache.org/bugzilla/show_bug.cgi?id=42580
This appears to be an relative edge case on Solaris 10 -- it hasn't
happened again, and it is a regression in APR, but relatively small, so
I am still +1 for httpd-2.2.9 shipping.
-Paul
---------------------------------------------------------------------
To unsubscribe, e-mail: testers-unsubscribe@httpd.apache.org
For additional commands, e-mail: testers-help@httpd.apache.org
Re: [VOTE] Release Apache HTTP Server 2.2.9
Posted by Paul Querna <ch...@force-elite.com>.
Jim Jagielski wrote:
> Test tarballs for Apache httpd 2.2.9 are available at:
>
> http://httpd.apache.org/dev/dist/
>
> Your votes please;
>
> +/-1
> [+1] Release httpd-2.2.9 as GA
+1 from me.
Upgraded {eos,aurora}.apache.org to 2.2.9 w/ the bundled APR:
http://eos.apache.org/server-status
http://aurora.apache.org/server-status
Both are Solaris 10/sparc.
These machines host www.apache.org and $tlp.apache.org.
Please let infrastructure know if you see any problems.
During the upgrade, it appears we hit one regression in APR 1.3.0.
On aurora.apache.org, shortly after installing the new version, we hit a
problem with apr_pollset_poll:
[Thu Jun 12 05:36:51 2008] [error] (70007)The timeout specified has
expired: apr_pollset_poll: (listen)
[Thu Jun 12 05:36:52 2008] [notice] caught SIGTERM, shutting down
If you look in worker.c, around line 687, you can see that if do a
graceful shutdown if we get an unexpected error from apr_pollset_poll.
This appears to be a regression caused by r641661:
https://svn.apache.org/viewvc?view=rev&revision=641661
Which was a fix for PR 42580:
https://issues.apache.org/bugzilla/show_bug.cgi?id=42580
This appears to be an relative edge case on Solaris 10 -- it hasn't
happened again, and it is a regression in APR, but relatively small, so
I am still +1 for httpd-2.2.9 shipping.
-Paul
Re: [VOTE] Release Apache HTTP Server 2.2.9
Posted by Jorge Schrauwen <jo...@gmail.com>.
On Wed, Jun 11, 2008 at 5:22 AM, William A. Rowe, Jr. <wr...@rowe-clan.net>
wrote:
> Jim Jagielski wrote:
>
>> Your votes please;
>>
>> +/-1
>> [+1] Release httpd-2.2.9 as GA
>>
>
> I'll rely on others to review linux, solaris, et al, but based on Win32 I'm
> very happy and just waiting for feedback from my prior questions to post up
> the various files.
>
Yes, windows seems fine... didn't test with ssl though.
--
~Jorge
Re: [VOTE] Release Apache HTTP Server 2.2.9
Posted by "William A. Rowe, Jr." <wr...@rowe-clan.net>.
Jim Jagielski wrote:
> Your votes please;
>
> +/-1
> [+1] Release httpd-2.2.9 as GA
I'll rely on others to review linux, solaris, et al, but based on Win32 I'm
very happy and just waiting for feedback from my prior questions to post up
the various files.
---------------------------------------------------------------------
To unsubscribe, e-mail: testers-unsubscribe@httpd.apache.org
For additional commands, e-mail: testers-help@httpd.apache.org
Re: [VOTE] Release Apache HTTP Server 2.2.9
Posted by Jorge Schrauwen <jo...@gmail.com>.
Ok did a new build with openssl on vs 2008 on vista.
It still give me hell over ipv6... there is a patch that fixes it!
https://issues.apache.org/bugzilla/attachment.cgi?id=21320&action=edit
with this patch it works fine following the basic steps of converting the
source (lineends.pl), perl cvtdsp.pl -2005
devenv Apache.dsw (to get command line building to work with vs2008)
for that point on it compiles fine from command line.
I've placed my binaries here for anyone that wants to do some heavier
testing on them (will be gone tomorrow):
*http://cygnus.gotdns.org/ (note: pdb's are included - very slow upload...
home server)*
I only tested the out of box config.
Jorge
On Wed, Jun 11, 2008 at 10:08 AM, Jorge Schrauwen <jo...@gmail.com>
wrote:
>
>
> On Wed, Jun 11, 2008 at 9:16 AM, Issac Goldstand <ma...@beamartyr.net>
> wrote:
>
>>
>>
>> Jim Jagielski wrote:
>>
>>> Test tarballs for Apache httpd 2.2.9 are available at:
>>>
>>> http://httpd.apache.org/dev/dist/
>>>
>>> Your votes please;
>>>
>>> +/-1
>>> [ ] Release httpd-2.2.9 as GA
>>>
>>> ----
>>>
>>> +1 Tested prefork + worker on linux with no problems. If I get a chance
>> to test win32 before the vote closes, I will, but based on Jorge's tests +
>> Bill's satisfaction with win32, I'm happy as long as noone -1s it.
>>
>
> I did have some problems with using vs 2008... I had to grab back to 2005.
> I'll give it a spin with ssl later this evening if I got time.
>
>
>>
>> Issac
>>
>
>
>
> --
> ~Jorge
--
~Jorge
Re: [VOTE] Release Apache HTTP Server 2.2.9
Posted by Jorge Schrauwen <jo...@gmail.com>.
On Wed, Jun 11, 2008 at 9:16 AM, Issac Goldstand <ma...@beamartyr.net>
wrote:
>
>
> Jim Jagielski wrote:
>
>> Test tarballs for Apache httpd 2.2.9 are available at:
>>
>> http://httpd.apache.org/dev/dist/
>>
>> Your votes please;
>>
>> +/-1
>> [ ] Release httpd-2.2.9 as GA
>>
>> ----
>>
>> +1 Tested prefork + worker on linux with no problems. If I get a chance
> to test win32 before the vote closes, I will, but based on Jorge's tests +
> Bill's satisfaction with win32, I'm happy as long as noone -1s it.
>
I did have some problems with using vs 2008... I had to grab back to 2005.
I'll give it a spin with ssl later this evening if I got time.
>
> Issac
>
--
~Jorge
Re: [VOTE] Release Apache HTTP Server 2.2.9
Posted by Issac Goldstand <ma...@beamartyr.net>.
Jim Jagielski wrote:
> Test tarballs for Apache httpd 2.2.9 are available at:
>
> http://httpd.apache.org/dev/dist/
>
> Your votes please;
>
> +/-1
> [ ] Release httpd-2.2.9 as GA
>
> ----
>
+1 Tested prefork + worker on linux with no problems. If I get a chance
to test win32 before the vote closes, I will, but based on Jorge's tests
+ Bill's satisfaction with win32, I'm happy as long as noone -1s it.
Issac
Re: [VOTE] Release Apache HTTP Server 2.2.9
Posted by Jim Jagielski <ji...@jaguNET.com>.
On Jun 10, 2008, at 8:50 PM, Jim Jagielski wrote:
> Test tarballs for Apache httpd 2.2.9 are available at:
>
> http://httpd.apache.org/dev/dist/
>
> Your votes please;
>
> +/-1
> [ ] Release httpd-2.2.9 as GA
>
+1
---------------------------------------------------------------------
To unsubscribe, e-mail: testers-unsubscribe@httpd.apache.org
For additional commands, e-mail: testers-help@httpd.apache.org
Re: [VOTE] Release Apache HTTP Server 2.2.9
Posted by Sander Temme <sc...@apache.org>.
On Jun 10, 2008, at 6:50 PM, Jim Jagielski wrote:
> +/-1
> [ ] Release httpd-2.2.9 as GA
+1 for release.
Darwin Legadema.local 9.3.0 Darwin Kernel Version 9.3.0: Fri May 23
00:49:16 PDT 2008; root:xnu-1228.5.18~1/RELEASE_I386 i386
2.2.9 Worker:
Failed Test Stat Wstat Total Fail List of Failed
-------------------------------------------------------------------------------
t/ssl/v2.t 1 1 1
3 tests and 2 subtests skipped.
Failed 1/80 test scripts. 1/2894 subtests failed.
Files=80, Tests=2894, 197 wallclock secs (39.79 cusr + 6.31 csys =
46.10 CPU)
Failed 1/80 test programs. 1/2894 subtests failed.
I get the same error (bad mac decode) when running the openssl command-
line tool. Probably something wrong with my OpenSSL:
[sctemme@Legadema] c-examples $ openssl s_client -ssl2 -connect
127.0.0.1:8532
CONNECTED(00000003)
depth=0 /C=US/ST=California/L=San Francisco/O=ASF/OU=httpd-test/rsa-test/CN=localhost/emailAddress=test-dev@httpd.apache.org
verify error:num=20:unable to get local issuer certificate
verify return:1
depth=0 /C=US/ST=California/L=San Francisco/O=ASF/OU=httpd-test/rsa-test/CN=localhost/emailAddress=test-dev@httpd.apache.org
verify error:num=27:certificate not trusted
verify return:1
depth=0 /C=US/ST=California/L=San Francisco/O=ASF/OU=httpd-test/rsa-test/CN=localhost/emailAddress=test-dev@httpd.apache.org
verify error:num=21:unable to verify the first certificate
verify return:1
80250:error:140EC071:SSL routines:SSL2_READ_INTERNAL:bad mac
decode:s2_pkt.c:274:
[sctemme@Legadema] c-examples $ openssl version
OpenSSL 0.9.7l 28 Sep 2006
[sctemme@Legadema] c-examples $ which openssl
/usr/bin/openssl
Apache's log:
[Tue Jun 10 22:12:59 2008] [debug] ssl_engine_kernel.c(1789): OpenSSL:
Exit: error in SSLv2 read client finished A
[Tue Jun 10 22:12:59 2008] [debug] ssl_engine_kernel.c(1789): OpenSSL:
Exit: error in SSLv2 read client finished A
[Tue Jun 10 22:12:59 2008] [info] [client 127.0.0.1] SSL library error
1 in handshake (server localhost:8532)
[Tue Jun 10 22:12:59 2008] [info] SSL Library Error: 336511089 error:
140EC071:SSL routines:SSL2_READ_INTERNAL:bad mac decode Browser still
remembered details of a re-created server certificate?
[Tue Jun 10 22:12:59 2008] [info] [client 127.0.0.1] Connection closed
to child 1 with abortive shutdown (server localhost:8532)
SSLv3 works.
FreeBSD legadema-bsd 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Sun Feb 24
19:59:52 UTC 2008 root@logan.cse.buffalo.edu:/usr/obj/usr/src/sys/
GENERIC i386
2.2.9 Prefork:
All tests successful, 3 tests and 2 subtests skipped.
Yay! +1
--
Sander Temme
sctemme@apache.org
PGP FP: 51B4 8727 466A 0BC3 69F4 B7B8 B2BE BC40 1529 24AF
Re: [VOTE] Release Apache HTTP Server 2.2.9
Posted by Jim Jagielski <ji...@jaguNET.com>.
On Jun 10, 2008, at 8:50 PM, Jim Jagielski wrote:
> Test tarballs for Apache httpd 2.2.9 are available at:
>
> http://httpd.apache.org/dev/dist/
>
> Your votes please;
>
> +/-1
> [ ] Release httpd-2.2.9 as GA
>
+1
Re: [VOTE] Release Apache HTTP Server 2.2.9
Posted by Jim Jagielski <ji...@jaguNET.com>.
On Jun 11, 2008, at 6:24 AM, Niklas Edmundsson wrote:
> On Tue, 10 Jun 2008, Jim Jagielski wrote:
>
>> Test tarballs for Apache httpd 2.2.9 are available at:
>>
>> http://httpd.apache.org/dev/dist/
>>
>> Your votes please;
>
> Out of curiosity, when does the voting close?
>
I'd like to release Friday, noon eastern.
Re: [VOTE] Release Apache HTTP Server 2.2.9
Posted by Niklas Edmundsson <ni...@acc.umu.se>.
On Tue, 10 Jun 2008, Jim Jagielski wrote:
> Test tarballs for Apache httpd 2.2.9 are available at:
>
> http://httpd.apache.org/dev/dist/
>
> Your votes please;
Out of curiosity, when does the voting close?
/Nikke - a bit bogged down at the moment
--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Niklas Edmundsson, Admin @ {acc,hpc2n}.umu.se | nikke@acc.umu.se
---------------------------------------------------------------------------
DIME: A dollar after taxes.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Re: [VOTE] Release Apache HTTP Server 2.2.9
Posted by Niklas Edmundsson <ni...@acc.umu.se>.
On Tue, 10 Jun 2008, Jim Jagielski wrote:
> [+1] Release httpd-2.2.9 as GA
Works OK on Ubuntu 8.04 'Hardy' x86 32bit (Linux 2.6.24-18-server on
dual socket Pentium4), it's one of the ftp.acc.umu.se offloaders so
it's getting production load without falling on its head or corrupting
files.
Also seems to work on AIX 5.3 TL7 SP3 (built with vac.C 9.0.0.4 using
cc) on a quad-core POWER4 machine, lightly tested.
Both builds are with the worker MPM.
/Nikke
--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Niklas Edmundsson, Admin @ {acc,hpc2n}.umu.se | nikke@acc.umu.se
---------------------------------------------------------------------------
KPLA Klingon Radio : All glory, all the time!
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Re: [VOTE] Release Apache HTTP Server 2.2.9
Posted by Rainer Jung <ra...@kippdata.de>.
Jim Jagielski schrieb:
> Test tarballs for Apache httpd 2.2.9 are available at:
>
> http://httpd.apache.org/dev/dist/
>
> Your votes please;
>
> +/-1
> [ ] Release httpd-2.2.9 as GA
+1 (non-binding)
Tested on Solaris 8 Sparc with latest test framework (without "-ssl").
No failures, but a couple of tests skipped due to missing
modules/filters (expected):
t/filter/case...............skipped
all skipped: cannot find module 'case_filter'
t/filter/case_in............skipped
all skipped: cannot find module 'case_filter_in'
t/http11/chunked2...........skipped
all skipped: cannot find module 'bucketeer'
t/modules/dav...............skipped
all skipped: cannot find module 'HTTP::DAV'
14/87 skipped: Skipping bucket boundary tests, no mod_bucketeer
t/php/all...................skipped
all skipped: cannot find one of php4 or php5 or sapi_apache2.c
t/protocol/echo.............skipped
all skipped: cannot find module 'mod_echo'
t/security/CVE-2004-0958....skipped
all skipped: cannot find one of php4 or php5 or sapi_apache2.c
t/security/CVE-2004-0959....skipped
all skipped: cannot find one of php4 or php5 or sapi_apache2.c,
PHP not installed
1/3 skipped: server gave HTTP/0.9 response
1/2 skipped: server gave HTTP/0.9 response
t/ssl/pr12355...............ok
2/10 skipped: mod_case_filter_in not available
All tests successful, 8 tests and 18 subtests skipped.
Rainer
Re: [VOTE] Release Apache HTTP Server 2.2.9
Posted by Nick Kew <ni...@webthing.com>.
On Tue, 10 Jun 2008 20:50:50 -0400
Jim Jagielski <ji...@jaguNET.com> wrote:
> Test tarballs for Apache httpd 2.2.9 are available at:
>
> http://httpd.apache.org/dev/dist/
>
> Your votes please;
Successfully installed and tested on Solaris, Linux, and OSX.
The coadvisor suite shows three new failures (note - failures
mean tests that don't complete successfully; protocol
violations are a different classification altogether).
These are tests involving sending 17 interim responses,
which we now reject, so I'm satisfied it's not a regression.
--
Nick Kew
Application Development with Apache - the Apache Modules Book
http://www.apachetutor.org/
Re: [VOTE] Release Apache HTTP Server 2.2.9
Posted by "William A. Rowe, Jr." <wr...@rowe-clan.net>.
Jim Jagielski wrote:
> Your votes please;
>
> +/-1
> [+1] Release httpd-2.2.9 as GA
I'll rely on others to review linux, solaris, et al, but based on Win32 I'm
very happy and just waiting for feedback from my prior questions to post up
the various files.
Re: [VOTE] Release Apache HTTP Server 2.2.9
Posted by Ruediger Pluem <rp...@apache.org>.
On 06/11/2008 02:50 AM, Jim Jagielski wrote:
> Test tarballs for Apache httpd 2.2.9 are available at:
>
> http://httpd.apache.org/dev/dist/
>
> Your votes please;
>
> +/-1
> [ +1 ] Release httpd-2.2.9 as GA
Here are my results:
Summary:
Solaris 8, 9 on SPARC, 32 bit build, gcc 3.3.2, using Solaris LDAP SDK:
Worker MPM, compiles, installs and starts fine
Solaris 10 on SPARC, 32 bit build, gcc 3.3.2:
Prefork, worker and event compile and install fine.
Prefork, worker and event pass all tests as far as the default
perl installation of Solaris 10 permits.
RedHat AS 3 32 bit:
Prefork, worker and event compile and install fine.
It does NOT compile with the RedHat included openldap 2.0.27-17.
More details later.
Event MPM does NOT start as epoll does not seem to work correctly.
Although the appropriate functions seem to be present they do
not seem to work. Configure from APR detected this and set epoll
support to 0, but there is no build check on httpd side to detect
this. Maybe a possible area of improvement.
Prefork and worker pass all tests (not including WebDAV as the needed
perl components are missing)
RedHat As 4 32 bit:
Prefork, worker and event compile and install fine.
Prefork, worker and event pass all tests (not including WebDAV as the needed
perl components are missing). Works fine with the included openldap 2.2.x.
RedHat As 4 64 bit:
Prefork, worker and event compile and install fine.
Prefork, worker and event pass all tests (not including WebDAV as the needed
perl components are missing). Works fine with the included openldap 2.2.x.
SuSE Linux 10.2 32 bit:
worker compiles and installs fine.
worker passes all tests. Works fine with the included openldap 2.3.x.
So all in all I am +1 for releasing.
Details:
Warnings reported on Solaris:
Solaris 8:
passwd/apr_getpass.c:97: warning: `get_password' defined but not used
threadproc/unix/thread.c: In function `apr_thread_once_init':
threadproc/unix/thread.c:306: warning: missing braces around initializer
threadproc/unix/thread.c:306: warning: (near initialization for `once_init.__pthread_once_pad')
xmlparse.c:7: warning: `RCSId' defined but not used
xmltok.c:7: warning: `RCSId' defined but not used
xmlrole.c:7: warning: `RCSId' defined but not used
dbd/apr_dbd.c: In function `apr_dbd_prepare':
dbd/apr_dbd.c:372: warning: subscript has type `char'
dbd/apr_dbd.c:388: warning: subscript has type `char'
ldap/apr_ldap_option.c: In function `option_set_cert':
ldap/apr_ldap_option.c:401: warning: unused variable `ents'
ldap/apr_ldap_option.c:402: warning: unused variable `i'
ldap/apr_ldap_rebind.c:187: warning: `apr_ldap_rebind_lookup' defined but not used
worker.c: In function `start_threads':
worker.c:1033: warning: int format, pid_t arg (arg 7)
worker.c: In function `make_child':
worker.c:1358: warning: int format, pid_t arg (arg 7)
worker.c: In function `ap_mpm_run':
worker.c:1669: warning: int format, pid_t arg (arg 4)
worker.c:1766: warning: int format, pid_t arg (arg 8)
worker.c:1793: warning: int format, pid_t arg (arg 8)
util.c: In function `ap_append_pid':
util.c:2146: warning: int format, pid_t arg (arg 5)
mpm_common.c: In function `reclaim_one_pid':
mpm_common.c:151: warning: int format, pid_t arg (arg 7)
mpm_common.c:161: warning: int format, pid_t arg (arg 7)
mpm_common.c:186: warning: int format, pid_t arg (arg 7)
mpm_common.c: In function `ap_process_child_status':
mpm_common.c:440: warning: int format, pid_t arg (arg 7)
mpm_common.c: In function `ap_signal_server':
mpm_common.c:991: warning: int format, pid_t arg (arg 3)
mpm_common.c:996: warning: int format, pid_t arg (arg 3)
mod_authnz_ldap.c: In function `authn_ldap_check_password':
mod_authnz_ldap.c:373: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c:378: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c:383: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c:390: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c:415: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c:471: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c:475: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c: In function `authz_ldap_check_user_access':
mod_authnz_ldap.c:540: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c:564: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c:623: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c:635: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c:642: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c:655: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c:662: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c:673: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c:682: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c:689: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c:703: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c:718: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c:724: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c:733: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c:740: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c:751: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c:760: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c:768: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c:776: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c:787: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c:793: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c:806: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c:816: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c:824: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c:832: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c:842: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c:848: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c:853: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c: In function `mod_auth_ldap_parse_url':
mod_authnz_ldap.c:876: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c:885: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c:887: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c:889: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c:891: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c:896: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c:898: warning: int format, pid_t arg (arg 7)
util_ldap.c: In function `util_ldap_set_cache_bytes':
util_ldap.c:1350: warning: int format, pid_t arg (arg 7)
util_ldap.c: In function `util_ldap_set_cache_ttl':
util_ldap.c:1397: warning: int format, pid_t arg (arg 7)
util_ldap.c: In function `util_ldap_set_cache_entries':
util_ldap.c:1421: warning: int format, pid_t arg (arg 7)
util_ldap.c: In function `util_ldap_set_opcache_ttl':
util_ldap.c:1442: warning: int format, pid_t arg (arg 7)
util_ldap.c: In function `util_ldap_set_opcache_entries':
util_ldap.c:1466: warning: int format, pid_t arg (arg 7)
util_ldap.c: In function `util_ldap_child_init':
util_ldap.c:2052: warning: int format, pid_t arg (arg 8)
mod_log_forensic.c: In function `log_before':
mod_log_forensic.c:199: warning: int format, pid_t arg (arg 3)
proxy_util.c: In function `ap_proxy_initialize_worker_share':
proxy_util.c:1851: warning: int format, pid_t arg (arg 8)
proxy_util.c:1856: warning: int format, pid_t arg (arg 8)
proxy_util.c:1864: warning: int format, pid_t arg (arg 7)
proxy_util.c: In function `ap_proxy_initialize_worker':
proxy_util.c:1953: warning: int format, pid_t arg (arg 8)
proxy_util.c:1969: warning: int format, pid_t arg (arg 8)
mod_proxy_balancer.c: In function `get_cookie_param':
mod_proxy_balancer.c:162: warning: subscript has type `char'
mod_proxy_balancer.c:165: warning: subscript has type `char'
mod_status.c: In function `status_handler':
mod_status.c:544: warning: int format, long int arg (arg 3)
mod_status.c:623: warning: int format, pid_t arg (arg 5)
mod_status.c:709: warning: int format, pid_t arg (arg 5)
mod_cgid.c: In function `cgid_server':
mod_cgid.c:701: warning: int format, pid_t arg (arg 7)
mod_cgid.c: In function `cleanup_nonchild_process':
mod_cgid.c:1245: warning: int format, pid_t arg (arg 7)
mod_cgid.c:1252: warning: int format, pid_t arg (arg 7)
Solaris 9:
passwd/apr_getpass.c:97: warning: `get_password' defined but not used
threadproc/unix/thread.c: In function `apr_thread_once_init':
threadproc/unix/thread.c:306: warning: missing braces around initializer
threadproc/unix/thread.c:306: warning: (near initialization for `once_init.__pthread_once_pad')
xmlparse.c:7: warning: `RCSId' defined but not used
xmltok.c:7: warning: `RCSId' defined but not used
xmlrole.c:7: warning: `RCSId' defined but not used
dbd/apr_dbd.c: In function `apr_dbd_prepare':
dbd/apr_dbd.c:372: warning: subscript has type `char'
dbd/apr_dbd.c:388: warning: subscript has type `char'
ldap/apr_ldap_rebind.c:187: warning: `apr_ldap_rebind_lookup' defined but not used
worker.c: In function `start_threads':
worker.c:1033: warning: int format, pid_t arg (arg 7)
worker.c: In function `make_child':
worker.c:1358: warning: int format, pid_t arg (arg 7)
worker.c: In function `ap_mpm_run':
worker.c:1669: warning: int format, pid_t arg (arg 4)
worker.c:1766: warning: int format, pid_t arg (arg 8)
worker.c:1793: warning: int format, pid_t arg (arg 8)
util.c: In function `ap_append_pid':
util.c:2146: warning: int format, pid_t arg (arg 5)
mpm_common.c: In function `reclaim_one_pid':
mpm_common.c:151: warning: int format, pid_t arg (arg 7)
mpm_common.c:161: warning: int format, pid_t arg (arg 7)
mpm_common.c:186: warning: int format, pid_t arg (arg 7)
mpm_common.c: In function `ap_process_child_status':
mpm_common.c:440: warning: int format, pid_t arg (arg 7)
mpm_common.c: In function `ap_signal_server':
mpm_common.c:991: warning: int format, pid_t arg (arg 3)
mpm_common.c:996: warning: int format, pid_t arg (arg 3)
mod_authnz_ldap.c: In function `authn_ldap_check_password':
mod_authnz_ldap.c:373: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c:378: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c:383: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c:390: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c:415: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c:471: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c:475: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c: In function `authz_ldap_check_user_access':
mod_authnz_ldap.c:540: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c:564: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c:623: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c:635: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c:642: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c:655: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c:662: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c:673: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c:682: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c:689: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c:703: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c:718: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c:724: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c:733: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c:740: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c:751: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c:760: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c:768: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c:776: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c:787: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c:793: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c:806: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c:816: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c:824: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c:832: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c:842: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c:848: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c:853: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c: In function `mod_auth_ldap_parse_url':
mod_authnz_ldap.c:876: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c:885: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c:887: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c:889: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c:891: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c:896: warning: int format, pid_t arg (arg 7)
mod_authnz_ldap.c:898: warning: int format, pid_t arg (arg 7)
util_ldap.c: In function `util_ldap_set_cache_bytes':
util_ldap.c:1350: warning: int format, pid_t arg (arg 7)
util_ldap.c: In function `util_ldap_set_cache_ttl':
util_ldap.c:1397: warning: int format, pid_t arg (arg 7)
util_ldap.c: In function `util_ldap_set_cache_entries':
util_ldap.c:1421: warning: int format, pid_t arg (arg 7)
util_ldap.c: In function `util_ldap_set_opcache_ttl':
util_ldap.c:1442: warning: int format, pid_t arg (arg 7)
util_ldap.c: In function `util_ldap_set_opcache_entries':
util_ldap.c:1466: warning: int format, pid_t arg (arg 7)
util_ldap.c: In function `util_ldap_child_init':
util_ldap.c:2052: warning: int format, pid_t arg (arg 8)
mod_log_forensic.c: In function `log_before':
mod_log_forensic.c:199: warning: int format, pid_t arg (arg 3)
proxy_util.c: In function `ap_proxy_initialize_worker_share':
proxy_util.c:1851: warning: int format, pid_t arg (arg 8)
proxy_util.c:1856: warning: int format, pid_t arg (arg 8)
proxy_util.c:1864: warning: int format, pid_t arg (arg 7)
proxy_util.c: In function `ap_proxy_initialize_worker':
proxy_util.c:1953: warning: int format, pid_t arg (arg 8)
proxy_util.c:1969: warning: int format, pid_t arg (arg 8)
mod_proxy_balancer.c: In function `get_cookie_param':
mod_proxy_balancer.c:162: warning: subscript has type `char'
mod_proxy_balancer.c:165: warning: subscript has type `char'
mod_status.c: In function `status_handler':
mod_status.c:544: warning: int format, long int arg (arg 3)
mod_status.c:623: warning: int format, pid_t arg (arg 5)
mod_status.c:709: warning: int format, pid_t arg (arg 5)
mod_cgid.c: In function `cgid_server':
mod_cgid.c:701: warning: int format, pid_t arg (arg 7)
mod_cgid.c: In function `cleanup_nonchild_process':
mod_cgid.c:1245: warning: int format, pid_t arg (arg 7)
mod_cgid.c:1252: warning: int format, pid_t arg (arg 7)
Solaris 10:
worker.c: In function `start_threads':
worker.c:1033: Warnung: int Format, pid_t Argument (Argument 7)
worker.c: In function `make_child':
worker.c:1358: Warnung: int Format, pid_t Argument (Argument 7)
worker.c: In function `ap_mpm_run':
worker.c:1669: Warnung: int Format, pid_t Argument (Argument 4)
worker.c:1766: Warnung: int Format, pid_t Argument (Argument 8)
worker.c:1793: Warnung: int Format, pid_t Argument (Argument 8)
util.c: In function `ap_append_pid':
util.c:2146: Warnung: int Format, pid_t Argument (Argument 5)
mpm_common.c: In function `reclaim_one_pid':
mpm_common.c:151: Warnung: int Format, pid_t Argument (Argument 7)
mpm_common.c:161: Warnung: int Format, pid_t Argument (Argument 7)
mpm_common.c:186: Warnung: int Format, pid_t Argument (Argument 7)
mpm_common.c: In function `ap_process_child_status':
mpm_common.c:440: Warnung: int Format, pid_t Argument (Argument 7)
mpm_common.c: In function `ap_signal_server':
mpm_common.c:991: Warnung: int Format, pid_t Argument (Argument 3)
mpm_common.c:996: Warnung: int Format, pid_t Argument (Argument 3)
mod_authnz_ldap.c: In function `authn_ldap_check_password':
mod_authnz_ldap.c:373: Warnung: int Format, pid_t Argument (Argument 7)
mod_authnz_ldap.c:378: Warnung: int Format, pid_t Argument (Argument 7)
mod_authnz_ldap.c:383: Warnung: int Format, pid_t Argument (Argument 7)
mod_authnz_ldap.c:390: Warnung: int Format, pid_t Argument (Argument 7)
mod_authnz_ldap.c:415: Warnung: int Format, pid_t Argument (Argument 7)
mod_authnz_ldap.c:471: Warnung: int Format, pid_t Argument (Argument 7)
mod_authnz_ldap.c:475: Warnung: int Format, pid_t Argument (Argument 7)
mod_authnz_ldap.c: In function `authz_ldap_check_user_access':
mod_authnz_ldap.c:540: Warnung: int Format, pid_t Argument (Argument 7)
mod_authnz_ldap.c:564: Warnung: int Format, pid_t Argument (Argument 7)
mod_authnz_ldap.c:623: Warnung: int Format, pid_t Argument (Argument 7)
mod_authnz_ldap.c:635: Warnung: int Format, pid_t Argument (Argument 7)
mod_authnz_ldap.c:642: Warnung: int Format, pid_t Argument (Argument 7)
mod_authnz_ldap.c:655: Warnung: int Format, pid_t Argument (Argument 7)
mod_authnz_ldap.c:662: Warnung: int Format, pid_t Argument (Argument 7)
mod_authnz_ldap.c:673: Warnung: int Format, pid_t Argument (Argument 7)
mod_authnz_ldap.c:682: Warnung: int Format, pid_t Argument (Argument 7)
mod_authnz_ldap.c:689: Warnung: int Format, pid_t Argument (Argument 7)
mod_authnz_ldap.c:703: Warnung: int Format, pid_t Argument (Argument 7)
mod_authnz_ldap.c:718: Warnung: int Format, pid_t Argument (Argument 7)
mod_authnz_ldap.c:724: Warnung: int Format, pid_t Argument (Argument 7)
mod_authnz_ldap.c:733: Warnung: int Format, pid_t Argument (Argument 7)
mod_authnz_ldap.c:740: Warnung: int Format, pid_t Argument (Argument 7)
mod_authnz_ldap.c:751: Warnung: int Format, pid_t Argument (Argument 7)
mod_authnz_ldap.c:760: Warnung: int Format, pid_t Argument (Argument 7)
mod_authnz_ldap.c:768: Warnung: int Format, pid_t Argument (Argument 7)
mod_authnz_ldap.c:776: Warnung: int Format, pid_t Argument (Argument 7)
mod_authnz_ldap.c:787: Warnung: int Format, pid_t Argument (Argument 7)
mod_authnz_ldap.c:793: Warnung: int Format, pid_t Argument (Argument 7)
mod_authnz_ldap.c:806: Warnung: int Format, pid_t Argument (Argument 7)
mod_authnz_ldap.c:816: Warnung: int Format, pid_t Argument (Argument 7)
mod_authnz_ldap.c:824: Warnung: int Format, pid_t Argument (Argument 7)
mod_authnz_ldap.c:832: Warnung: int Format, pid_t Argument (Argument 7)
mod_authnz_ldap.c:842: Warnung: int Format, pid_t Argument (Argument 7)
mod_authnz_ldap.c:848: Warnung: int Format, pid_t Argument (Argument 7)
mod_authnz_ldap.c:853: Warnung: int Format, pid_t Argument (Argument 7)
mod_authnz_ldap.c: In function `mod_auth_ldap_parse_url':
mod_authnz_ldap.c:876: Warnung: int Format, pid_t Argument (Argument 7)
mod_authnz_ldap.c:885: Warnung: int Format, pid_t Argument (Argument 7)
mod_authnz_ldap.c:887: Warnung: int Format, pid_t Argument (Argument 7)
mod_authnz_ldap.c:889: Warnung: int Format, pid_t Argument (Argument 7)
mod_authnz_ldap.c:891: Warnung: int Format, pid_t Argument (Argument 7)
mod_authnz_ldap.c:896: Warnung: int Format, pid_t Argument (Argument 7)
mod_authnz_ldap.c:898: Warnung: int Format, pid_t Argument (Argument 7)
util_ldap.c: In function `util_ldap_set_cache_bytes':
util_ldap.c:1350: Warnung: int Format, pid_t Argument (Argument 7)
util_ldap.c: In function `util_ldap_set_cache_ttl':
util_ldap.c:1397: Warnung: int Format, pid_t Argument (Argument 7)
util_ldap.c: In function `util_ldap_set_cache_entries':
util_ldap.c:1421: Warnung: int Format, pid_t Argument (Argument 7)
util_ldap.c: In function `util_ldap_set_opcache_ttl':
util_ldap.c:1442: Warnung: int Format, pid_t Argument (Argument 7)
util_ldap.c: In function `util_ldap_set_opcache_entries':
util_ldap.c:1466: Warnung: int Format, pid_t Argument (Argument 7)
util_ldap.c: In function `util_ldap_child_init':
util_ldap.c:2052: Warnung: int Format, pid_t Argument (Argument 8)
mod_log_forensic.c: In function `log_before':
mod_log_forensic.c:199: Warnung: int Format, pid_t Argument (Argument 3)
proxy_util.c: In function `ap_proxy_initialize_worker_share':
proxy_util.c:1851: Warnung: int Format, pid_t Argument (Argument 8)
proxy_util.c:1856: Warnung: int Format, pid_t Argument (Argument 8)
proxy_util.c:1864: Warnung: int Format, pid_t Argument (Argument 7)
proxy_util.c: In function `ap_proxy_initialize_worker':
proxy_util.c:1953: Warnung: int Format, pid_t Argument (Argument 8)
proxy_util.c:1969: Warnung: int Format, pid_t Argument (Argument 8)
mod_status.c: In function `status_handler':
mod_status.c:544: Warnung: int Format, long int Argument (Argument 3)
mod_status.c:623: Warnung: int Format, pid_t Argument (Argument 5)
mod_status.c:709: Warnung: int Format, pid_t Argument (Argument 5)
mod_cgid.c: In function `cgid_server':
mod_cgid.c:701: Warnung: int Format, pid_t Argument (Argument 7)
mod_cgid.c: In function `cleanup_nonchild_process':
mod_cgid.c:1245: Warnung: int Format, pid_t Argument (Argument 7)
mod_cgid.c:1252: Warnung: int Format, pid_t Argument (Argument 7)
As far as I remember all apr / apr-util related warnings should
be fixed in apr / apr-util trunk (r663342 / r663344), but r663344
is not backported to 1.3.x yet.
RedHAT AS 3
The failure of the build against openldap 2.0.27:
ldap/apr_ldap_rebind.c: In function `apr_ldap_rebind_set_callback':
ldap/apr_ldap_rebind.c:288: warning: passing arg 2 of `ldap_set_rebind_proc' from incompatible pointer type
ldap/apr_ldap_rebind.c:288: too many arguments to function `ldap_set_rebind_proc'
make[3]: *** [ldap/apr_ldap_rebind.lo] Error 1
make[2]: *** [all-recursive] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all-recursive] Error 1
This seems to be an issue with apr-util 1.3.0. It seems that the API of
openldap has changed between 2.0.x and 2.2.x. Maybe we should check in apr-util's
configure script that a usable version of openldap is present.
Regards
Rüdiger
Re: [VOTE] Release Apache HTTP Server 2.2.9
Posted by André Malo <nd...@perlig.de>.
* William A. Rowe, Jr. wrote:
> André Malo wrote:
> > Well, for the pure (online) HTML distribution manual.css,
> > manual-print.css and manual-loose-100pc.css should be sufficient.
> > The *zip* CSS files are modifications for static distributions and the
> > *chm* file for the CHM build.
> >
> > I suggest however to blacklist the (CSS) files you want to kick instead
> > of whitelisting the used ones. That way there's less room for mistakes
> > :)
>
> /shrug - I'm thinking it's not really worth it to even bother to axe
> these, they are small and harmless and generally not confusing, unlike
> the other noise I mentioned which are confusing enough for me to have to
> ask :)
fair enough ;)
nd
--
Da fällt mir ein, wieso gibt es eigentlich in Unicode kein
"i" mit einem Herzchen als Tüpfelchen? Das wär sooo süüss!
-- Björn Höhrmann in darw
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org
Re: [VOTE] Release Apache HTTP Server 2.2.9
Posted by "William A. Rowe, Jr." <wr...@rowe-clan.net>.
André Malo wrote:
>
> Well, for the pure (online) HTML distribution manual.css, manual-print.css
> and manual-loose-100pc.css should be sufficient.
> The *zip* CSS files are modifications for static distributions and the *chm*
> file for the CHM build.
>
> I suggest however to blacklist the (CSS) files you want to kick instead of
> whitelisting the used ones. That way there's less room for mistakes :)
/shrug - I'm thinking it's not really worth it to even bother to axe these,
they are small and harmless and generally not confusing, unlike the other
noise I mentioned which are confusing enough for me to have to ask :)
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org
Re: [VOTE] Release Apache HTTP Server 2.2.9
Posted by André Malo <nd...@perlig.de>.
* William A. Rowe, Jr. wrote:
> Jim Jagielski wrote:
> > Test tarballs for Apache httpd 2.2.9 are available at:
> >
> > http://httpd.apache.org/dev/dist/
>
> I've reviewed the result set of our roll release script, which axes all
> of the .xml/.xsl inputs, and this leftover group of files seem odd...
>
> httpd-2.2.9\manual\style\build.properties
> httpd-2.2.9\manual\style\common.dtd
> httpd-2.2.9\manual\style\faq.dtd
> httpd-2.2.9\manual\style\lang.dtd
> httpd-2.2.9\manual\style\manualpage.dtd
> httpd-2.2.9\manual\style\modulesynopsis.dtd
> httpd-2.2.9\manual\style\sitemap.dtd
> httpd-2.2.9\manual\style\version.ent
> httpd-2.2.9\manual\style\latex
> httpd-2.2.9\manual\style\latex\atbeginend.sty
>
> can someone confirm that all of these should be axed in an html result
> tree from our roll/release script? If so, I'll modify it.
confirmed.
>
> The only things I'm sure we want to retain under the manual/style
> tree are...
>
> httpd-2.2.9\manual\style\css
> httpd-2.2.9\manual\style\css\manual-chm.css
> httpd-2.2.9\manual\style\css\manual-loose-100pc.css
> httpd-2.2.9\manual\style\css\manual-print.css
> httpd-2.2.9\manual\style\css\manual-zip-100pc.css
> httpd-2.2.9\manual\style\css\manual-zip.css
> httpd-2.2.9\manual\style\css\manual.css
Well, for the pure (online) HTML distribution manual.css, manual-print.css
and manual-loose-100pc.css should be sufficient.
The *zip* CSS files are modifications for static distributions and the *chm*
file for the CHM build.
I suggest however to blacklist the (CSS) files you want to kick instead of
whitelisting the used ones. That way there's less room for mistakes :)
nd
--
"Solides und umfangreiches Buch"
-- aus einer Rezension
<http://pub.perlig.de/books.html#apache2>
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org
Re: [VOTE] Release Apache HTTP Server 2.2.9
Posted by "William A. Rowe, Jr." <wr...@rowe-clan.net>.
Jim Jagielski wrote:
> Test tarballs for Apache httpd 2.2.9 are available at:
>
> http://httpd.apache.org/dev/dist/
I've reviewed the result set of our roll release script, which axes all
of the .xml/.xsl inputs, and this leftover group of files seem odd...
httpd-2.2.9\manual\style\build.properties
httpd-2.2.9\manual\style\common.dtd
httpd-2.2.9\manual\style\faq.dtd
httpd-2.2.9\manual\style\lang.dtd
httpd-2.2.9\manual\style\manualpage.dtd
httpd-2.2.9\manual\style\modulesynopsis.dtd
httpd-2.2.9\manual\style\sitemap.dtd
httpd-2.2.9\manual\style\version.ent
httpd-2.2.9\manual\style\latex
httpd-2.2.9\manual\style\latex\atbeginend.sty
can someone confirm that all of these should be axed in an html result
tree from our roll/release script? If so, I'll modify it.
The only things I'm sure we want to retain under the manual/style
tree are...
httpd-2.2.9\manual\style\css
httpd-2.2.9\manual\style\css\manual-chm.css
httpd-2.2.9\manual\style\css\manual-loose-100pc.css
httpd-2.2.9\manual\style\css\manual-print.css
httpd-2.2.9\manual\style\css\manual-zip-100pc.css
httpd-2.2.9\manual\style\css\manual-zip.css
httpd-2.2.9\manual\style\css\manual.css
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org
Re: *** GMX Spamverdacht *** Re: [RESULT] (Was: Re: [VOTE] Release Apache HTTP Server 2.2.9)
Posted by Jim Jagielski <ji...@jaguNET.com>.
I was hoping that mirrors would have all synced up by
tonight, but looking at the rate, I doubt it...
On Jun 13, 2008, at 4:03 PM, Ruediger Pluem wrote:
> As the site already offers 2.2.9 for download, I would say tonight.
>
> Regards
>
> Rüdiger
>
> On 06/13/2008 09:12 PM, Jim Jagielski wrote:
>> The tarballs and site files are being pushed to the mirrors...
>> Announce tonight or tomorrow??
>
Re: *** GMX Spamverdacht *** Re: [RESULT] (Was: Re: [VOTE] Release
Apache HTTP Server 2.2.9)
Posted by Ruediger Pluem <rp...@apache.org>.
As the site already offers 2.2.9 for download, I would say tonight.
Regards
Rüdiger
On 06/13/2008 09:12 PM, Jim Jagielski wrote:
> The tarballs and site files are being pushed to the mirrors...
>
> Announce tonight or tomorrow??
>
>
Re: [RESULT] (Was: Re: [VOTE] Release Apache HTTP Server 2.2.9)
Posted by Jorge Schrauwen <jo...@gmail.com>.
On Fri, Jun 13, 2008 at 9:58 PM, Joshua Slive <jo...@slive.ca> wrote:
> On Fri, Jun 13, 2008 at 3:49 PM, Jorge Schrauwen
> <jo...@gmail.com> wrote:
> > I'd say tomorrow so most mirrors will be synced by then... unless they
> sync
> > very fast... no idea how fast that is.
>
> You can see a histogram of last-sync times near the bottom of this page:
> http://www.apache.org/mirrors/
> Most mirrors sync at least every 12 hours and essentially all sync
> within 24 hours.
>
Oh I never noticed that.
Knowing this I'd still answer the question the same... wait for tomorrow.
No that it matters much what I think ^^ but every opinion seems to count so
I'll voice it anyway.
~Jorge
Re: [RESULT] (Was: Re: [VOTE] Release Apache HTTP Server 2.2.9)
Posted by Joshua Slive <jo...@slive.ca>.
On Fri, Jun 13, 2008 at 3:49 PM, Jorge Schrauwen
<jo...@gmail.com> wrote:
> I'd say tomorrow so most mirrors will be synced by then... unless they sync
> very fast... no idea how fast that is.
You can see a histogram of last-sync times near the bottom of this page:
http://www.apache.org/mirrors/
Most mirrors sync at least every 12 hours and essentially all sync
within 24 hours.
Re: [RESULT] (Was: Re: [VOTE] Release Apache HTTP Server 2.2.9)
Posted by Jorge Schrauwen <jo...@gmail.com>.
I'd say tomorrow so most mirrors will be synced by then... unless they sync
very fast... no idea how fast that is.
~Jorge
On Fri, Jun 13, 2008 at 9:12 PM, Jim Jagielski <ji...@jagunet.com> wrote:
> The tarballs and site files are being pushed to the mirrors...
>
> Announce tonight or tomorrow??
>
Re: [RESULT] (Was: Re: [VOTE] Release Apache HTTP Server 2.2.9)
Posted by Jim Jagielski <ji...@jaguNET.com>.
The tarballs and site files are being pushed to the mirrors...
Announce tonight or tomorrow??
[RESULT] (Was: Re: [VOTE] Release Apache HTTP Server 2.2.9)
Posted by Jim Jagielski <ji...@jaguNET.com>.
On Jun 10, 2008, at 8:50 PM, Jim Jagielski wrote:
> Test tarballs for Apache httpd 2.2.9 are available at:
>
> http://httpd.apache.org/dev/dist/
>
> Your votes please;
>
> +/-1
> [ ] Release httpd-2.2.9 as GA
>
With plenty of +1s (eg: jim, sctemme, issac, bnicholes,
rpluem, pquerna, niq, wrowe) and no -1s, I call the vote
CLOSED, with the result of approving the release of
2.2.9 as GA.
Re: [VOTE] Release Apache HTTP Server 2.2.9
Posted by Brad Nicholes <BN...@novell.com>.
>>> On 6/10/2008 at 6:50 PM, in message
<2A...@jaguNET.com>, Jim Jagielski
<ji...@jaguNET.com> wrote:
> Test tarballs for Apache httpd 2.2.9 are available at:
>
> http://httpd.apache.org/dev/dist/
>
> Your votes please;
>
> +/-1
> [ ] Release httpd-2.2.9 as GA
>
> ----
>
> DO NOT begin distributing these in any manner whatsoever, please note
> that
> you can seriously mess up any user who installs these packages if they
> are
> ultimately rejected.
+1 NetWare
---------------------------------------------------------------------
To unsubscribe, e-mail: testers-unsubscribe@httpd.apache.org
For additional commands, e-mail: testers-help@httpd.apache.org
Re: [VOTE] Release Apache HTTP Server 2.2.9
Posted by Brad Nicholes <BN...@novell.com>.
>>> On 6/10/2008 at 6:50 PM, in message
<2A...@jaguNET.com>, Jim Jagielski
<ji...@jaguNET.com> wrote:
> Test tarballs for Apache httpd 2.2.9 are available at:
>
> http://httpd.apache.org/dev/dist/
>
> Your votes please;
>
> +/-1
> [ ] Release httpd-2.2.9 as GA
>
> ----
>
> DO NOT begin distributing these in any manner whatsoever, please note
> that
> you can seriously mess up any user who installs these packages if they
> are
> ultimately rejected.
+1 NetWare
Re: [VOTE] Release Apache HTTP Server 2.2.9
Posted by Oden Eriksson <oe...@mandriva.com>.
Den Wednesday 11 June 2008 02:50:50 skrev Jim Jagielski:
> Test tarballs for Apache httpd 2.2.9 are available at:
>
> http://httpd.apache.org/dev/dist/
>
> Your votes please;
>
> +/-1
> [ ] Release httpd-2.2.9 as GA
>
> ----
>
> DO NOT begin distributing these in any manner whatsoever, please note
> that
> you can seriously mess up any user who installs these packages if they
> are
> ultimately rejected.
With latest perl-framework, apr/apu I get this on Mandriva Cooker x86_64:
t/apache/limits.............NOK 7/10# Failed test 7 in t/apache/limits.t at
line 122
t/apache/limits.............NOK 9/10# Failed test 9 in t/apache/limits.t at
line 122 fail #2
t/apache/limits.............FAILED tests 7, 9
Failed 2/10 tests, 80.00% okay
The t/apache/limits tests passes on Mandriva Linux 2008.1 though.
The openssl tests passed with the fix pointed out by
Rainer Jung (2.2.9 testing with OpenSSL 0.9.8h). Thanks man.
Funny enough I get this as well:
t/security/CVE-2008-2364....NOK 2/3# Failed test 2 in
t/security/CVE-2008-2364.t at line 19
t/security/CVE-2008-2364....NOK 3/3# Failed test 3 in
t/security/CVE-2008-2364.t at line 22
t/security/CVE-2008-2364....FAILED tests 2-3
Failed 2/3 tests, 33.33% okay
--
Regards // Oden Eriksson