On 10/17/2018 03:25 PM, William A Rowe Jr wrote:
https://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x/ is what
will be exported, ,/buildconf invoked, and then tarred up, if that helps
you anticipate the tag a day early. It shouldn't give any different
hassles than trunk.
thank you,
https://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x/ is what will
be exported, ,/buildconf invoked, and then tarred up, if that helps you
anticipate the tag a day early. It shouldn't give any different hassles
than trunk.
On Wed, Oct 17, 2018, 13:31 Dennis Clarke wrote:
> On 10/17/2018
On 10/17/2018 02:24 PM, Daniel Ruggeri wrote:
On 2018-10-17 13:13, Dennis Clarke wrote:
On 10/17/2018 07:41 AM, Daniel Ruggeri wrote:
Hi, all;
With the fix for detected OpenSSL 1.1.1 issues now backported to
2.4.x, I would like to tag the next version of our venerable server
soon.
I have
On 2018-10-17 13:13, Dennis Clarke wrote:
On 10/17/2018 07:41 AM, Daniel Ruggeri wrote:
Hi, all;
With the fix for detected OpenSSL 1.1.1 issues now backported to
2.4.x, I would like to tag the next version of our venerable server
soon.
I have already successfully completed the test suite
On 10/17/2018 07:41 AM, Daniel Ruggeri wrote:
Hi, all;
With the fix for detected OpenSSL 1.1.1 issues now backported to 2.4.x,
I would like to tag the next version of our venerable server soon.
I have already successfully completed the test suite against my "latest
sources" docker
On Wed, Oct 17, 2018 at 03:32:34PM +0100, Joe Orton wrote:
> I see constant memory use for a simple PROPFIND/depth:1 for the
> attached, though I'm not sure this is sufficient to repro the problem
> you saw before.
I needed to also remove the new apr_pool_clear() there. Is the repro
case for
On Fri, Oct 12, 2018 at 4:54 PM William A Rowe Jr
wrote:
> Great, I'll proceed with changing ab.c to remove the hack, since it is
> unneeded when ab.c is compiled by the same toolchain as libcrypto.dll,
> isn't available in non-openssl distributions, and was deprecated in 1.1.1
> again.
>
Note,
On 17/10/2018 15:44, Joe Orton wrote:
> On Wed, Oct 17, 2018 at 02:29:42PM +0200, jean-frederic clere wrote:
>> One of the customer complains is that having the variables exposed like
>> in StdEnvars has a huge performances cost (everything is exposed for
>> each request) , he wants to check one
On Tue, Oct 16, 2018 at 02:28:06PM +0200, Ruediger Pluem wrote:
> Gentle ping :-). Did you find some time to have a look?
"I'm not Greg, but..."
This seems to be duplicating the ctx->scratchpool which was added for
use in dav_propfind_walker specifically to solve this kind of problem, I
think?
On Wed, Oct 17, 2018 at 02:29:42PM +0200, jean-frederic clere wrote:
> One of the customer complains is that having the variables exposed like
> in StdEnvars has a huge performances cost (everything is exposed for
> each request) , he wants to check one variable and then decide in his
> code what
On 16/10/2018 19:21, Ruediger Pluem wrote:
>
>
> On 10/16/2018 02:53 PM, jfcl...@apache.org wrote:
>> Author: jfclere
>> Date: Tue Oct 16 12:53:18 2018
>> New Revision: 1844001
>>
>> URL: http://svn.apache.org/viewvc?rev=1844001=rev
>> Log:
>> And a way to custom modules to guess and extract ssl
On 17/10/2018 12:44, Joe Orton wrote:
> On Tue, Oct 16, 2018 at 07:21:54PM +0200, Ruediger Pluem wrote:
>> On 10/16/2018 02:53 PM, jfcl...@apache.org wrote:
>>> Author: jfclere
>>> Date: Tue Oct 16 12:53:18 2018
>>> New Revision: 1844001
>>>
>>> URL: http://svn.apache.org/viewvc?rev=1844001=rev
Am 17.10.2018 um 13:41 schrieb Daniel Ruggeri:
Hi, all;
With the fix for detected OpenSSL 1.1.1 issues now backported to 2.4.x,
I would like to tag the next version of our venerable server soon.
I have already successfully completed the test suite against my "latest
sources" docker
I like the idea. It took a bit of ruminating to get there, but the thought of
shipping new features in odds and fixes/stabilizations in evens (or something
along those lines) feels comfortable. I would personally prefer a semver
release style where we burn minors often-ish, but haven't been
> Am 17.10.2018 um 13:43 schrieb Graham Leggett :
>
> On 17 Oct 2018, at 13:41, Daniel Ruggeri wrote:
>
>> Hi, all;
>> With the fix for detected OpenSSL 1.1.1 issues now backported to 2.4.x, I
>> would like to tag the next version of our venerable server soon.
>>
>> I have already
On 17 Oct 2018, at 13:41, Daniel Ruggeri wrote:
> Hi, all;
> With the fix for detected OpenSSL 1.1.1 issues now backported to 2.4.x, I
> would like to tag the next version of our venerable server soon.
>
> I have already successfully completed the test suite against my "latest
> sources"
Hi, all;
With the fix for detected OpenSSL 1.1.1 issues now backported to 2.4.x, I
would like to tag the next version of our venerable server soon.
I have already successfully completed the test suite against my "latest
sources" docker environment and am watching for any smoke detected in
Thank you so much for your thorough work.
One of these days I'd love to hear all about your testing setup. It would so
cool to run something similar on our buildbot!
--
Daniel Ruggeri
On October 17, 2018 3:01:11 AM CDT, Rainer Jung wrote:
>Thanks.
>
>I'm doing new builds now for a bunch of
On Tue, Oct 16, 2018 at 07:21:54PM +0200, Ruediger Pluem wrote:
> On 10/16/2018 02:53 PM, jfcl...@apache.org wrote:
> > Author: jfclere
> > Date: Tue Oct 16 12:53:18 2018
> > New Revision: 1844001
> >
> > URL: http://svn.apache.org/viewvc?rev=1844001=rev
> > Log:
> > And a way to custom modules
> Am 15.10.2018 um 13:45 schrieb Luca Toscano :
>
> Hi everybody,
>
> apologies if this subject has been brought up in the past but I didn't
> find much. I have been working on some bugs like
> https://bz.apache.org/bugzilla/show_bug.cgi?id=62380 in which users
> report responses with the
Thanks.
I'm doing new builds now for a bunch of OpenSSL versions and shared plus
static linking (but only the reallyall module set). Then I will run the
test suite, combining each with a bunch of OpenSSL versions used in the
client (perl modules).
I guess those runs will take until
21 matches
Mail list logo
