On Tue, Mar 7, 2017 at 1:37 PM, Jacob Champion wrote:
> On 03/07/2017 07:49 AM, William A Rowe Jr wrote:
>>
>> Ok, adding /usr/lib is a bad thing any and every day (and in this case,
>> completely bogus since it lives in /usr/lib64).
>
>
> Same on Ubuntu, where the actual
On Tue, Mar 7, 2017 at 3:24 PM, Jacob Champion wrote:
> Getting 2.4.x going will require some backports, so I'm planning to look
> into running the test suite against trunk (probably not next week but the
> week after). Unless there's anyone who *really* wants 2.4.x
On 02/02/2017 12:22 PM, Jacob Champion wrote:
Every commit you make to trunk (well, group of commits, within
fifteen seconds of each other) is run through an incremental build,
which takes about ten seconds. Every eight hours, the build tree is
clobbered, resync'd, and built from scratch, which
On 02/28/2017 04:32 PM, Jacob Champion wrote:
I just don't like hamstringing a nice new directive with what's
effectively a (rare) bug.
(The conversation kinda died shortly after I said this. That was not my
intent -- I like this directive a lot. Whether the consensus is to keep
the corner
On 03/07/2017 07:49 AM, William A Rowe Jr wrote:
Ok, adding /usr/lib is a bad thing any and every day (and in this case,
completely bogus since it lives in /usr/lib64).
Same on Ubuntu, where the actual libraries live in an
architecture-specific folder under /usr/lib.
But I'm still not
On 03/07/2017 04:33 AM, Jim Jagielski wrote:
Backport away! :)
Done (and veto rescinded); thanks for bearing with me over the speed
bump. :)
--Jacob
On Tue, Mar 7, 2017 at 12:59 PM, Stefan Fritsch wrote:
> On Tuesday, 7 March 2017 11:17:57 CET Eric Covener wrote:
>> On Tue, Mar 7, 2017 at 10:32 AM, William A Rowe Jr
> wrote:
>> > It seems we should have the framework process the bin/envvars (in the
>> >
On Tuesday, 7 March 2017 12:56:04 CET William A Rowe Jr wrote:
> My comment was that having an alternate target name, e.g. httpd.prefork
> or httpd.worker ends up resulting in $prefix/conf/httpd.prefork.conf as the
> derived config file name (although that file is actually httpd.conf). The
> fact
On Tuesday, 7 March 2017 11:17:57 CET Eric Covener wrote:
> On Tue, Mar 7, 2017 at 10:32 AM, William A Rowe Jr
wrote:
> > It seems we should have the framework process the bin/envvars (in the
> > normal path, or /etc/apache2 in this case)... but that should be based
> > on
On Tue, Mar 7, 2017 at 10:17 AM, Eric Covener wrote:
> On Tue, Mar 7, 2017 at 10:32 AM, William A Rowe Jr
> wrote:
>> It seems we should have the framework process the bin/envvars (in the normal
>> path, or /etc/apache2 in this case)... but that should
If you're looking for a stop-gap for Ubuntu, apply my patch and tests start
running. :)
Or are you looking for a better stop-gap? I'm happy to make changes if you
can explain what needs to work differently.
Sam
On Tue, Mar 7, 2017 at 7:32 AM, William A Rowe Jr
wrote:
>
Six months ago, rjung forked 2.4.x and began to backport our
compatibility fixes for OpenSSL 1.1.0. Today, from the state of
trunk, it seems the compatibility efforts look very good and are
nearly ready to apply to 2.4.x. That branch-point was here;
On Tue, Mar 7, 2017 at 10:32 AM, William A Rowe Jr wrote:
> It seems we should have the framework process the bin/envvars (in the normal
> path, or /etc/apache2 in this case)... but that should be based on
> retrieving the
> pathname of bin/envvars from apxs, and apxs
Some oddities, pretty sure there is no regression though. Fedora's layout is;
/usr/include/
luaconf.hlua.hlualib.hluaconf-x86_64.hlua.hpp
/usr/include/lua-5.1/
lauxlib.h luaconf.h lua.h lua.hpp lualib.h
/usr/lib64/
/usr/lib64/liblua-5.1.so
/usr/lib64/libluajit-5.1.so.2 ->
On Mon, Mar 6, 2017 at 3:11 PM, Sam Tregar wrote:
> Are you suggesting that people who want to run tests that use Apache::Test
> should know that they have to source /etc/apache2/envvars first? Or that I
> should patch Apache::Test to source that file instead of guessing which
Backport away! :)
> On Mar 6, 2017, at 2:52 PM, Jacob Champion wrote:
>
> On 03/06/2017 09:41 AM, Jacob Champion wrote:
>> On 03/06/2017 04:36 AM, Jim Jagielski wrote:
>>> So config.m4 should look for that API then, right?
>>
>> Yup. I don't think it's *quite* as easy as
16 matches
Mail list logo