Why wasn't (hasn't) a version 2.0.3 been pushed out that just fixes problem with the tests? I only found out about this problem about 3 weeks ago, after going through the same banging of the head that so many other people seem to have. This problem has existed for months and seems like it could have been fixed in short order by just fixing the tests and pushing out a release. I have no idea what's involved with getting something like that to happen, but mod_ssl seems to do it with nearly every httpd release.
I don't mean to offend anyone, I just think this was treated like an insignificant thing, when for some new users it may be far from it. Adam -----Original Message----- From: Philip M. Gollucci [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 05, 2006 2:04 PM To: andy law (RI) Cc: modperl@perl.apache.org Subject: Re: Failing tests - a plea from the heart andy law (RI) wrote: > I've just finished beating my head against the modperl tests. I > understand that I'm not alone in having been down this route. No sir, you are not. Yes, both status. and content_length_header.t are fixed in SVN and will be fixed in the 2.0.3 release. > I also understand from trawling through the mailing list archives - a > not entirely pain-free procedure itself - that the mod_perl 'grown-ups' > are "getting tired" of answering questions about failing tests, > particularly those about content_length_header.t and status.t. HAHA Where were you when I asked if this would be useful ? At any rate, its been on my list for a while now -- just haven't gotten to it yet. > Also, I note from my trips through the archives that I am not alone in > thinking that the tests should work 'out of the box'. Darryl Miles - I > too feel your pain (and frustration). Well they do with those 2 exceptions which are from things that happened AFTER the release went public. > And all this pain would be prevented by the simple addition of a 'Known > issues with the tests' section on the web site. Heck, you even have a > section entitled "'make test' Failures" in the documents already. How > hard would it be to keep the current known issues up to date in this > document (or at least add a reference to a page on which they were > recorded)? Feel free to start it: To do this correctly, you need os-release compiler httpd version and mpm perl version and ithreads or not If I had my druthers, only the CURRENT release would be listed and MAYBE if its been fixed in SVN yet. -- ------------------------------------------------------------------------ Philip M. Gollucci ([EMAIL PROTECTED]) 323.219.4708 Consultant / http://p6m7g8.net/Resume/resume.shtml Senior Software Engineer - TicketMaster - http://ticketmaster.com 1024D/A79997FA F357 0FDD 2301 6296 690F 6A47 D55A 7172 A799 97F "In all that I've done wrong I know I must have done something right to deserve a hug every morning and butterfly kisses at night." __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / / /|_/ / // /\ \/ /_/ / /__ /_/ /_/\_, /___/\___\_\___/ <___/
