You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@perl.apache.org by Stas Bekman <st...@stason.org> on 2003/04/22 10:19:46 UTC
are we ready for 1.99_09 release?
Are there any showstoppers for 1.99_09 release? This question is related to
Apache::Test as well, since I want to release it on CPAN (for the first time)
simultaneously with 1.99_09.
If not, I'll post a release candidate tomorrow.
I did a few last minutes changes so please test well that I didn't break
anything. Especially the recent change in the build process that handles
systems where apr is installed in different location from httpd.
This release will endorse people to start porting their CPAN modules to 2.0,
since now we have ModPerl::MM which supports 3rd party 2.0 module builds.
It'll also deliver an almost complete filtering API (the missing bits are
several TIEHANDLE methods, which aren't very urgent to implement).
Thanks.
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: are we ready for 1.99_09 release?
Posted by Stas Bekman <st...@stason.org>.
Geoffrey Young wrote:
>
>> Are you talking about Apache 2.1 or Apache 2.0? I've updated the
>> APACHE_2_0_BRANCH and I don't see this problem. You must be using the
>> very unstable, bleading edge HEAD which is really Apache 2.1. I won't
>> bother about excluding this test for now. Apache 2.1 is not for
>> production use.
>
>
> yeah, the cvs HEAD from cvs.apache.org, which I guess is 2.1.
It is. See: http://httpd.apache.org/dev/devnotes.html
> bleedperl, apache cvs, and mod_perl cvs recompiled nightly :)
Cool, but it'd be more practical to use the nightly build of APACHE_2_0_BRANCH
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: are we ready for 1.99_09 release?
Posted by Geoffrey Young <ge...@modperlcookbook.org>.
> Are you talking about Apache 2.1 or Apache 2.0? I've updated the
> APACHE_2_0_BRANCH and I don't see this problem. You must be using the
> very unstable, bleading edge HEAD which is really Apache 2.1. I won't
> bother about excluding this test for now. Apache 2.1 is not for
> production use.
yeah, the cvs HEAD from cvs.apache.org, which I guess is 2.1.
bleedperl, apache cvs, and mod_perl cvs recompiled nightly :)
--Geoff
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: are we ready for 1.99_09 release?
Posted by Stas Bekman <st...@stason.org>.
Stas Bekman wrote:
> Geoffrey Young wrote:
>
>>
>>
>> Stas Bekman wrote:
>>
>>> Are there any showstoppers for 1.99_09 release?
>>
>>
>>
>> not that I'm aware of. the only issue I've been having lately is that
>> Registry's 206.t has been dumping core on me with Apache CVS HEAD
>> (backtrace below).
Are you talking about Apache 2.1 or Apache 2.0? I've updated the
APACHE_2_0_BRANCH and I don't see this problem. You must be using the very
unstable, bleading edge HEAD which is really Apache 2.1. I won't bother about
excluding this test for now. Apache 2.1 is not for production use.
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: are we ready for 1.99_09 release?
Posted by Stas Bekman <st...@stason.org>.
Geoffrey Young wrote:
>
>
> Stas Bekman wrote:
>
>> Are there any showstoppers for 1.99_09 release?
>
>
> not that I'm aware of. the only issue I've been having lately is that
> Registry's 206.t has been dumping core on me with Apache CVS HEAD
> (backtrace below).
OK, Thanks Geoff.
> if someone else can verify this, maybe we can add some skips for 206.t
> and the part of perlio.t that's failing on un-threaded perls before
> release.
Yes, I was planning to exclude perlio.t from the distro and so for another
test that dumps core with blead perl (filter/out_str_req_mix.t).
> #0 0x4001bb0a in apr_brigade_writev (b=0x10, flush=0, ctx=0x0,
> vec=0xbffff290, nvec=4) at apr_brigade.c:502
> #1 0x807017c in form_header_field (h=0xbffff2d8, fieldname=0x80a6416
> "Date", fieldval=0x88032d0 "Fri, 31 Jan 2003 09:39:01 GMT")
> at http_protocol.c:1165
> #2 0x80703ed in basic_http_header (r=0x87f7a08, bb=0x8803598,
> protocol=0x80a6372 "HTTP/1.1") at http_protocol.c:1289
> #3 0x8070d2c in ap_http_header_filter (f=0x87f8810, b=0x88033e0) at
> http_protocol.c:1685
> #4 0x80913ea in ap_pass_brigade (next=0x87f8810, bb=0x88033e0) at
> util_filter.c:550
> #5 0x80937a6 in ap_content_length_filter (f=0x87f87f8, b=0x88033e0) at
> protocol.c:1250
> #6 0x80913ea in ap_pass_brigade (next=0x87f87f8, bb=0x88033e0) at
> util_filter.c:550
> #7 0x8072afd in ap_byterange_filter (f=0x87f87e0, bb=0x88033e0) at
> http_protocol.c:3053
> #8 0x80913ea in ap_pass_brigade (next=0x87f87e0, bb=0x88033e0) at
> util_filter.c:550
> #9 0x4028c85c in modperl_wbucket_pass (wb=0x8800cb8,
> buf=0x8800cbc "Status: 206 Partial Content\nContent-Type: text/html;
> charset=UTF-8\nContent-Length: 11\nContent-Range: bytes 0-10/1336\nDate:
> Fri, 31 Jan 2003 09:39:01 GMT\nETag: \"xxxx\"\n\n<?xml versi", len=11,
> add_flush_bucket=0) at modperl_filter.c:150
For some reason, the cgi header wasn't parsed, but sent as is. I'll update my
head and meanwhile exclude this test from the distro.
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: are we ready for 1.99_09 release?
Posted by Geoffrey Young <ge...@modperlcookbook.org>.
Stas Bekman wrote:
> Are there any showstoppers for 1.99_09 release?
not that I'm aware of. the only issue I've been having lately is that
Registry's 206.t has been dumping core on me with Apache CVS HEAD
(backtrace below).
if someone else can verify this, maybe we can add some skips for 206.t and
the part of perlio.t that's failing on un-threaded perls before release.
> This question is related
> to Apache::Test as well, since I want to release it on CPAN (for the
> first time) simultaneously with 1.99_09.
1.99_09 is a good idea, as is an official Apache::Test CPAN release to match.
>
> If not, I'll post a release candidate tomorrow.
cool!
--Geoff
#0 0x4001bb0a in apr_brigade_writev (b=0x10, flush=0, ctx=0x0,
vec=0xbffff290, nvec=4) at apr_brigade.c:502
#1 0x807017c in form_header_field (h=0xbffff2d8, fieldname=0x80a6416
"Date", fieldval=0x88032d0 "Fri, 31 Jan 2003 09:39:01 GMT")
at http_protocol.c:1165
#2 0x80703ed in basic_http_header (r=0x87f7a08, bb=0x8803598,
protocol=0x80a6372 "HTTP/1.1") at http_protocol.c:1289
#3 0x8070d2c in ap_http_header_filter (f=0x87f8810, b=0x88033e0) at
http_protocol.c:1685
#4 0x80913ea in ap_pass_brigade (next=0x87f8810, bb=0x88033e0) at
util_filter.c:550
#5 0x80937a6 in ap_content_length_filter (f=0x87f87f8, b=0x88033e0) at
protocol.c:1250
#6 0x80913ea in ap_pass_brigade (next=0x87f87f8, bb=0x88033e0) at
util_filter.c:550
#7 0x8072afd in ap_byterange_filter (f=0x87f87e0, bb=0x88033e0) at
http_protocol.c:3053
#8 0x80913ea in ap_pass_brigade (next=0x87f87e0, bb=0x88033e0) at
util_filter.c:550
#9 0x4028c85c in modperl_wbucket_pass (wb=0x8800cb8,
buf=0x8800cbc "Status: 206 Partial Content\nContent-Type: text/html;
charset=UTF-8\nContent-Length: 11\nContent-Range: bytes 0-10/1336\nDate:
Fri, 31 Jan 2003 09:39:01 GMT\nETag: \"xxxx\"\n\n<?xml versi", len=11,
add_flush_bucket=0) at modperl_filter.c:150
#10 0x4028c8a8 in modperl_wbucket_flush (wb=0x8800cb8, add_flush_bucket=0)
at modperl_filter.c:165
#11 0x402809d3 in modperl_response_finish (r=0x87f7a08) at mod_perl.c:768
#12 0x40280ccb in modperl_response_handler_cgi (r=0x87f7a08) at mod_perl.c:860
#13 0x8084d52 in ap_run_handler (r=0x87f7a08) at config.c:194
#14 0x8085383 in ap_invoke_handler (r=0x87f7a08) at config.c:401
#15 0x8072f7f in ap_process_request (r=0x87f7a08) at http_request.c:288
#16 0x806e6e4 in ap_process_http_connection (c=0x87f3ac0) at http_core.c:292
#17 0x808eedc in ap_run_process_connection (c=0x87f3ac0) at connection.c:85
#18 0x808f1c1 in ap_process_connection (c=0x87f3ac0, csd=0x87f39f8) at
connection.c:211
#19 0x80837f2 in child_main (child_num_arg=0) at prefork.c:643
#20 0x808392b in make_child (s=0x80c4888, slot=0) at prefork.c:737
#21 0x8083991 in startup_children (number_to_start=1) at prefork.c:755
#22 0x8083d3b in ap_mpm_run (_pconf=0x80c1e30, plog=0x80f9f10, s=0x80c4888)
at prefork.c:971
#23 0x8089ad7 in main (argc=7, argv=0xbffff714) at main.c:671
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org