Re: svn commit: r1812303 - /httpd/httpd/branches/2.4.x/STATUS

2017-10-17 Thread Jim Jagielski
Let's keep :) > On Oct 16, 2017, at 11:54 PM, William A Rowe Jr wrote: > > Seems Jim is +0 to back out and I'm +0 to keep. First > strong opinion wins so we can get to tagging :) > > Absolute consensus on informing our apr, and httpd > builders what not to pass as CFLAGS, and why. > > > On Oc

expr changes and 2.4.29-dev

2017-10-17 Thread Jim Jagielski
HEAD of 2.4 now has errors with the test framework: t/apache/expr_string.t .. 1/32 # Failed test 27 in t/apache/expr_string.t at line 73 fail #10 # Failed test 28 in t/apache/expr_string.t at line 83 fail #9 # Failed test 29 in t/apache/expr_string.t at line 87 t/apache/expr_string.t

Re: expr changes and 2.4.29-dev

2017-10-17 Thread Jim Jagielski
verbose: # writing file: /Users/jim/src/asf/code/stable/httpd-test/framework/t/htdocs/apache/expr/.htaccess Error log should not have 'Internal evaluation error' or 'flex scanner jammed' entries, found 1: flex scanner jammed not ok 27 Expected return code 200, got 500 for '%{tolower:"IDENT"}' n

Potential output filter order of processing

2017-10-17 Thread Nick Gearls
Hello, I encounter a problem with the order of processing of output filters. Maybe I'm missing some background but there's something very weird. I'll show the example with mod_substitute but I imagine it's similar for other modules (although I'm not sure). Case 1:    Subst "s/x/1x/qn"    Subst

Re: Potential output filter order of processing

2017-10-17 Thread Eric Covener
On Tue, Oct 17, 2017 at 9:59 AM, Nick Gearls wrote: > Hello, > > I encounter a problem with the order of processing of output filters. > Maybe I'm missing some background but there's something very weird. > I'll show the example with mod_substitute but I imagine it's similar for > other modules (a

Re: expr changes and 2.4.29-dev

2017-10-17 Thread Joe Orton
On Tue, Oct 17, 2017 at 07:57:51AM -0400, Jim Jagielski wrote: > HEAD of 2.4 now has errors with the test framework: > > t/apache/expr_string.t .. 1/32 # Failed test 27 in > t/apache/expr_string.t at line 73 fail #10 > # Failed test 28 in t/apache/expr_string.t at line 83 fail #9 > #

Re: expr changes and 2.4.29-dev

2017-10-17 Thread Jim Jagielski
OK, this does not look like a regression, but instead a test not expected to PASS under 2.4 (yet). So I am thinking that a T&R of 2.4.29 is now a Go. I will likely T&R later on today, say ~3pm eastern.

Re: expr changes and 2.4.29-dev

2017-10-17 Thread Yann Ylavic
On Tue, Oct 17, 2017 at 5:51 PM, Joe Orton wrote: > On Tue, Oct 17, 2017 at 07:57:51AM -0400, Jim Jagielski wrote: >> HEAD of 2.4 now has errors with the test framework: >> >> t/apache/expr_string.t .. 1/32 # Failed test 27 in >> t/apache/expr_string.t at line 73 fail #10 >> # Failed

Re: expr changes and 2.4.29-dev

2017-10-17 Thread Yann Ylavic
On Tue, Oct 17, 2017 at 6:27 PM, Yann Ylavic wrote: > On Tue, Oct 17, 2017 at 5:51 PM, Joe Orton wrote: > >> I tweaked it to >> run for 2.5 only anyway. > > Jim reported three failures and you disabled one only, do the others > work for you? Hmm, it seems it depends :/ OK, I can reproduce, a sin

[VOTE] Release Apache httpd 2.4.29 as GA

2017-10-17 Thread Jim Jagielski
The pre-release test tarballs for Apache httpd version 2.4.29 can be found at the usual place: http://httpd.apache.org/dev/dist/ I'm calling a VOTE on releasing these as Apache httpd 2.4.29 GA. [ ] +1: Good to go [ ] +0: meh [ ] -1: Danger Will Robinson. And why. Vote will last the norm

Re: [VOTE] Release Apache httpd 2.4.29 as GA

2017-10-17 Thread Joe Orton
On Tue, Oct 17, 2017 at 03:00:36PM -0400, Jim Jagielski wrote: > The pre-release test tarballs for Apache httpd > version 2.4.29 can be found at the usual place: > > http://httpd.apache.org/dev/dist/ > > I'm calling a VOTE on releasing these as Apache httpd 2.4.29 GA. +1 - looks good on Fe

AW: svn commit: r1812393 - in /httpd/httpd/branches/2.4.x: ./ STATUS modules/http2/ modules/http2/config2.m4

2017-10-17 Thread Plüm , Rüdiger , Vodafone Group
Good point. The original desire was to have lib64 as fallback in order to keep the default as is with lib. But probably the reverse order (64 over 32) makes more sense these days. Keen to hear what others say. Regards Rüdiger Von: William A Rowe Jr [mailto:wr...@rowe-clan.net] Gesendet: Dienst