Re: NOTICE: Intent to T 2.4.35 in the next few hours

On 09/21/2018 09:52 AM, Daniel Ruggeri wrote: I've updated the proposed, generated announcements here: https://dist.apache.org/repos/dist/dev/httpd/Announcement2.4.html https://dist.apache.org/repos/dist/dev/httpd/Announcement2.4.txt A quick proofread would be appreciated - this should be the

Re: NOTICE: Intent to T 2.4.35 in the next few hours

On Fri, Sep 21, 2018 at 08:52:32AM -0500, Daniel Ruggeri wrote: > I've updated the proposed, generated announcements here: > https://dist.apache.org/repos/dist/dev/httpd/Announcement2.4.html > https://dist.apache.org/repos/dist/dev/httpd/Announcement2.4.txt > > A quick proofread would be

Re: NOTICE: Intent to T 2.4.35 in the next few hours

I've updated the proposed, generated announcements here: https://dist.apache.org/repos/dist/dev/httpd/Announcement2.4.html https://dist.apache.org/repos/dist/dev/httpd/Announcement2.4.txt A quick proofread would be appreciated - this should be the exact messages that will be sent/published. --

Re: NOTICE: Intent to T 2.4.35 in the next few hours

On Wed, Sep 19, 2018 at 6:56 AM Joe Orton wrote: > On Wed, Sep 19, 2018 at 01:19:29PM +0200, Apache Lounge wrote: > > Are there examples what (maybe) does not work with OpenSSL 1.1.1 ? > > Have you run the test suite? The flipped setting of SSL_MODE_AUTO_RETRY > is expected to break TLSv1.2 as

Re: NOTICE: Intent to T 2.4.35 in the next few hours

On Wed, Sep 19, 2018 at 01:19:29PM +0200, Apache Lounge wrote: > Are there examples what (maybe) does not work with OpenSSL 1.1.1 ? Have you run the test suite? The flipped setting of SSL_MODE_AUTO_RETRY is expected to break TLSv1.2 as well, that problem is consistent with the hangs Daniel

Re: NOTICE: Intent to T 2.4.35 in the next few hours

Are there examples what (maybe) does not work with OpenSSL 1.1.1 ? Build 2.4.35 with OpenSSL 1.1.1, no issues seen/reported. More then A week ago I ask already the community to test 2.4.34 with OpenSSL 1.1.1 also no issue reported. Plan to ship 2.4.35 with OpenSSL1.1.1 With our

Re: NOTICE: Intent to T 2.4.35 in the next few hours

+1 > Am 19.09.2018 um 12:54 schrieb Joe Orton : > > On Tue, Sep 18, 2018 at 11:19:10AM -0500, William A Rowe Jr wrote: >> On Tue, Sep 18, 2018 at 2:43 AM Joe Orton wrote: >>> You'll likely see issues testing against OpenSSL 1.1.1 until the TLSv1.3 >>> merge is integrated for 2.4.x, yeah, I

Re: NOTICE: Intent to T 2.4.35 in the next few hours

On 09/19/2018 12:54 PM, Joe Orton wrote: > On Tue, Sep 18, 2018 at 11:19:10AM -0500, William A Rowe Jr wrote: >> On Tue, Sep 18, 2018 at 2:43 AM Joe Orton wrote: >>> You'll likely see issues testing against OpenSSL 1.1.1 until the TLSv1.3 >>> merge is integrated for 2.4.x, yeah, I wouldn't

Re: NOTICE: Intent to T 2.4.35 in the next few hours

On Tue, Sep 18, 2018 at 11:19:10AM -0500, William A Rowe Jr wrote: > On Tue, Sep 18, 2018 at 2:43 AM Joe Orton wrote: > > You'll likely see issues testing against OpenSSL 1.1.1 until the TLSv1.3 > > merge is integrated for 2.4.x, yeah, I wouldn't worry about that. > > But I think this is worth

Re: NOTICE: Intent to T 2.4.35 in the next few hours

On Tue, Sep 18, 2018 at 1:56 PM Ruediger Pluem wrote: > > > You'll likely see issues testing against OpenSSL 1.1.1 until the > TLSv1.3 > > merge is integrated for 2.4.x, yeah, I wouldn't worry about that. > > > > > > But I think this is worth highlighting in our Announcement, that we

Re: NOTICE: Intent to T 2.4.35 in the next few hours

On 09/18/2018 06:19 PM, William A Rowe Jr wrote: > On Tue, Sep 18, 2018 at 2:43 AM Joe Orton > wrote: > > On Mon, Sep 17, 2018 at 06:16:34PM -0500, Daniel Ruggeri wrote: > >Sorry - I know it wasn't a very good report. I was just seeing if > > anyone

Re: NOTICE: Intent to T 2.4.35 in the next few hours

On Tue, Sep 18, 2018 at 2:43 AM Joe Orton wrote: > On Mon, Sep 17, 2018 at 06:16:34PM -0500, Daniel Ruggeri wrote: > >Sorry - I know it wasn't a very good report. I was just seeing if > > anyone has experienced a similar holdup. In fact, I let it run while > > tending to other things and

Re: NOTICE: Intent to T 2.4.35 in the next few hours

On Mon, Sep 17, 2018 at 06:16:34PM -0500, Daniel Ruggeri wrote: >    Sorry - I know it wasn't a very good report. I was just seeing if > anyone has experienced a similar holdup. In fact, I let it run while > tending to other things and came back to see it had completed (but > failed), so perhaps

Re: NOTICE: Intent to T 2.4.35 in the next few hours

On 9/17/2018 2:20 PM, Rainer Jung wrote: > Am 17.09.2018 um 20:59 schrieb Daniel Ruggeri: >> Hi, all; >>     I have been delayed executing the automation because the test >> suite seems to be hanging for me. This appears to be consistently >> during t/ssl/varlookup.t as that is the only process

Re: NOTICE: Intent to T 2.4.35 in the next few hours

Am 17.09.2018 um 20:59 schrieb Daniel Ruggeri: Hi, all;    I have been delayed executing the automation because the test suite seems to be hanging for me. This appears to be consistently during t/ssl/varlookup.t as that is the only process other than httpd running in this container during

Re: NOTICE: Intent to T 2.4.35 in the next few hours

Hi, all; I have been delayed executing the automation because the test suite seems to be hanging for me. This appears to be consistently during t/ssl/varlookup.t as that is the only process other than httpd running in this container during the hang. When killing httpd, the failures

Re: NOTICE: Intent to T 2.4.35 in the next few hours

On Mon, Sep 17, 2018 at 12:08 PM William A Rowe Jr wrote: > I'm similarly examining the win32 cmake build in anticipation. > > Thus far, the only issue is the mis-inclusion of applink.c; this is broken > with openssl 1.1.1. Looking now for a resolution. > There is an issue, but it seems

Re: NOTICE: Intent to T 2.4.35 in the next few hours

I'm similarly examining the win32 cmake build in anticipation. Thus far, the only issue is the mis-inclusion of applink.c; this is broken with openssl 1.1.1. Looking now for a resolution. On Mon, Sep 17, 2018 at 10:02 AM Daniel Ruggeri wrote: > Hi, all; > > STATUS is looking clean and my test

NOTICE: Intent to T 2.4.35 in the next few hours

Hi, all; STATUS is looking clean and my test suite is building/testing. Assuming those tests work out and life is happy, I will T 2.4.35 from 2.4.x branch in a few hours. I will also follow up in another couple weeks to T 2.4.36 if we can work in some of the newer features by then. --