On 2018/03/24 10:04, Chris Bennett wrote: > On Sat, Mar 24, 2018 at 01:04:16PM +0000, Stuart Henderson wrote: > > So 2.4.32 went away after I sent out my update diff, and yesterday > > 2.4.33 arrived in its place. Not much changed since 2.4.32 from which > > I've already had some positive test reports. (If my understanding of > > their process is correct they have a couple of releases with separate > > version numbers which would be similar to what many would do as an > > rc, then when happy they push one more publically as "the version > > people should use"). > > > > Opinions on updating now please? Push for release or hold off until > > stable? It's one of those things that typically only gets limited testing > > on ports@ but it feels like it's something more likely to be used by > > people who only run release.. > > > > Quite a roll of security fixes though most are unusual configs/hard > > to trigger. Info in https://www.apache.org/dist/httpd/CHANGES_2.4.33. > > FWIW, I am using the patch to make mod_perl work. > I haven't tested this :_( but I am getting a lot of child segmentation > faults in my error log. That may be a side effect of mod_perl. > I'm going to move away from Apache. Unless others are having problems > right now, it may be better to just wait for -stable. > > So, is anyone having similar problems with lots of odd errors right now? > Or am I just the odd case? > > If this will work with mod_perl and there is time, I can test it. > Just let me know. > > Chris Bennett > >
I'm only using Apache with svn here, which seems OK. I very much doubt if this update will make things any better with mod_perl.
