Re: [VOTE] Release httpd-2.4.53-rc1 as httpd-2.4.53

2022-03-08 Thread Ruediger Pluem
On 3/8/22 12:57 PM, Joe Orton wrote: > On Mon, Mar 07, 2022 at 04:55:54PM +0100, Stefan Eissing wrote: >> Hi all, >> >> Please find below the proposed release tarball and signatures: >> >> https://dist.apache.org/repos/dist/dev/httpd/ >> >> I would like to call a VOTE over the next few days to

Re: [VOTE] Release httpd-2.4.53-rc1 as httpd-2.4.53

2022-03-08 Thread Joe Orton
On Tue, Mar 08, 2022 at 02:01:42PM +0100, Ruediger Pluem wrote: > > I got a new "may be uninitialized" warning with with the GCC 12 shapshot > > used in Fedora 36 (which is still under development and can be > > unreliable). I think it's unreachable, if we enter here: > > > >

Re: [VOTE] Release httpd-2.4.53-rc1 as httpd-2.4.53

2022-03-08 Thread Stefan Eissing
For anyone thinking about testing rc1, there is a high chance of an rc2 coming soon. Will announce here, Stefan > Am 08.03.2022 um 16:33 schrieb Rainer Jung : > > > Am 07.03.2022 um 16:55 schrieb Stefan Eissing: >> Hi all, >> Please find below the proposed release tarball and signatures: >>

Re: [VOTE] Release httpd-2.4.53-rc1 as httpd-2.4.53

2022-03-08 Thread Ruediger Pluem
On 3/8/22 4:38 PM, Rainer Jung wrote: > Am 08.03.2022 um 16:33 schrieb Rainer Jung: >> >> Am 07.03.2022 um 16:55 schrieb Stefan Eissing: >>> Hi all, >>> >>> Please find below the proposed release tarball and signatures: >>> >>> https://dist.apache.org/repos/dist/dev/httpd/ >>> >>> I would like

Re: backports

2022-03-08 Thread Stefan Eissing
> Am 08.03.2022 um 14:34 schrieb Jim Jagielski : > >> On Mar 8, 2022, at 7:58 AM, Graham Leggett wrote: >> >> >> I would far rather the empty APLOGNO check was part of the build. >> >> Vastly simpler. >> > > I agree w/ that... I have the feeling that the work that has went into making

Re: backports

2022-03-08 Thread Graham Leggett
On 08 Mar 2022, at 10:29, Joe Orton wrote: >> “No need to patch/compile locally" is not a good idea - currently the >> travis tests target Ubuntu only, and this is a practical limitation >> forced upon us by the nature of the Travis service. I want to see >> reviewers try out the patch on

Re: [VOTE] Release httpd-2.4.53-rc1 as httpd-2.4.53

2022-03-08 Thread Rainer Jung
Am 08.03.2022 um 16:33 schrieb Rainer Jung: Am 07.03.2022 um 16:55 schrieb Stefan Eissing: Hi all, Please find below the proposed release tarball and signatures: https://dist.apache.org/repos/dist/dev/httpd/ I would like to call a VOTE over the next few days to release this candidate

Re: [VOTE] Release httpd-2.4.53-rc1 as httpd-2.4.53

2022-03-08 Thread Jim Jagielski
> On Mar 7, 2022, at 10:55 AM, Stefan Eissing wrote: > > Hi all, > > Please find below the proposed release tarball and signatures: > > https://dist.apache.org/repos/dist/dev/httpd/ > > I would like to call a VOTE over the next few days to release > this candidate tarball httpd-2.4.53-rc1

Re: backports

2022-03-08 Thread Jim Jagielski
> On Mar 8, 2022, at 7:58 AM, Graham Leggett wrote: > > > I would far rather the empty APLOGNO check was part of the build. > > Vastly simpler. > I agree w/ that...

Re: [VOTE] Release httpd-2.4.53-rc1 as httpd-2.4.53

2022-03-08 Thread Rainer Jung
Am 07.03.2022 um 16:55 schrieb Stefan Eissing: Hi all, Please find below the proposed release tarball and signatures: https://dist.apache.org/repos/dist/dev/httpd/ I would like to call a VOTE over the next few days to release this candidate tarball httpd-2.4.53-rc1 as 2.4.53: [ ] +1: It's

Re: [VOTE] Release httpd-2.4.53-rc1 as httpd-2.4.53

2022-03-08 Thread Joe Orton
On Mon, Mar 07, 2022 at 04:55:54PM +0100, Stefan Eissing wrote: > Hi all, > > Please find below the proposed release tarball and signatures: > > https://dist.apache.org/repos/dist/dev/httpd/ > > I would like to call a VOTE over the next few days to release > this candidate tarball

Re: [VOTE] Release httpd-2.4.53-rc1 as httpd-2.4.53

2022-03-08 Thread Rainer Jung
Am 08.03.2022 um 17:06 schrieb Ruediger Pluem: On 3/8/22 4:38 PM, Rainer Jung wrote: Am 08.03.2022 um 16:33 schrieb Rainer Jung: Am 07.03.2022 um 16:55 schrieb Stefan Eissing: Hi all, Please find below the proposed release tarball and signatures:

Re: backports

2022-03-08 Thread Eric Covener
> I have the feeling that the work that has went into making our > tests run on travis is not sufficiently honoured in this discussion. > > Looking back on the last 6 years I participated here, the situation > now is *vastly* improved to what we had before. For me, the Travis CI > status is now

Re: [VOTE] Release httpd-2.4.53-rc1 as httpd-2.4.53

2022-03-08 Thread Rainer Jung
Am 08.03.2022 um 18:22 schrieb Rainer Jung: Am 08.03.2022 um 17:06 schrieb Ruediger Pluem: On 3/8/22 4:38 PM, Rainer Jung wrote: Am 08.03.2022 um 16:33 schrieb Rainer Jung: Am 07.03.2022 um 16:55 schrieb Stefan Eissing: Hi all, Please find below the proposed release tarball and

Re: [VOTE] Release httpd-2.4.53-rc1 as httpd-2.4.53

2022-03-08 Thread Ruediger Pluem
On 3/8/22 10:09 PM, Rainer Jung wrote: > > > You gcc 4.8 workaround for _Thread_local still looks good. > > Solaris builds and all unit tests not yet done but compiles fine for all my > Linuxes. > > Thanks! Thanks for testing. I committed to trunk as r1898771 to throw it into our CI. If

Re: [VOTE] Release httpd-2.4.53-rc1 as httpd-2.4.53

2022-03-08 Thread Ruediger Pluem
On 3/8/22 10:09 PM, Rainer Jung wrote: > >> >> Two additional things I already saw, but which are non.critical: >> >> - configure flag --with-pcre no longer accepts an external pcre 8 >> installation directory. It seems in that case the flag must >> now point to the path of the pcre-config

Re: candidate branch/tag names

2022-03-08 Thread Joe Orton
On Mon, Mar 07, 2022 at 01:46:51PM +0100, Stefan Eissing wrote: > Joe, > > I'll change the release candidate tag/branch names and if that works, > you can strip some regex from the travis setup. Looks good to me, thanks Stefan. I've updated the regexes. Regards, Joe

Re: backports

2022-03-08 Thread Ruediger Pluem
On 3/7/22 12:23 PM, Joe Orton wrote: > > AIUI you can configure github to allow merges even if tests fail, though > I'm not familiar with that, has anybody played with the settings there? > Haven't played with them, but the below looks like a good starting point:

Re: backports

2022-03-08 Thread Joe Orton
On Fri, Mar 04, 2022 at 09:40:49AM -0800, Roy T. Fielding wrote: > > On Mar 4, 2022, at 6:17 AM, Eric Covener wrote: > > > > On Fri, Mar 4, 2022 at 9:05 AM Jim Jagielski wrote: > >> > >> A question: Would it be easier for all this if we moved to being Github > >> canon? > > > > I think it is

Re: backports

2022-03-08 Thread Joe Orton
On Mon, Mar 07, 2022 at 01:28:19PM +0200, Graham Leggett wrote: > On 07 Mar 2022, at 11:21, Stefan Eissing wrote: > > > I'd really like, as a reviewer of backports, you can: > > - see that it passes all our tests. No need to patch/compile/test locally. > > “No need to patch/compile locally" is

Re: svn commit: r1898566 - in /httpd/httpd/branches/2.4.x: ./ modules/aaa/ modules/cache/ modules/dav/fs/ modules/dav/lock/ modules/mappers/ modules/proxy/

2022-03-08 Thread Joe Orton
On Fri, Mar 04, 2022 at 09:24:37AM +0100, Stefan Eissing wrote: > > Am 04.03.2022 um 08:32 schrieb Ruediger Pluem : > > On 3/3/22 5:40 PM, Joe Orton wrote: > >> Oh, good question. I'm not sure how the "branch" variable appears in an > >> arbitrary branch but it's possible we'd need to tweak the

Re: backports

2022-03-08 Thread Joe Orton
On Sun, Mar 06, 2022 at 05:56:36PM +0200, Graham Leggett wrote: > I am however strongly opposed for Github to be our only promotion process. > > CI is great right until the point you get your first unrelated test failure, > then it is a nightmare. The collectd project was completely stuck unable