On 2018-10-18 07:12, Rainer Jung wrote:
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
Am 18.10.2018 um 14:23 schrieb Stefan Eissing:
Am 18.10.2018 um 14:12 schrieb Rainer Jung :
- t/modules/http2.t fails when the server is build using OpenSSL 0.9.8zh with the
"Bad plan. You planned 52 tests..." message indicating, that h2 using TLS does
not work. It happens on all
> Am 18.10.2018 um 14:12 schrieb Rainer Jung :
>
> - t/modules/http2.t fails when the server is build using OpenSSL 0.9.8zh with
> the "Bad plan. You planned 52 tests..." message indicating, that h2 using
> TLS does not work. It happens on all platforms, but not if the client also
> uses
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
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
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
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
> 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
14 matches
Mail list logo
