From: Michael J Gruber <git@drmicha.warpmail.net>
To: Eric Wong <normalperson@yhbt.net>
Cc: git@vger.kernel.org
Subject: Re: [WIP/RFH/PATCH 3/3] t/lib-git-svn: adjust config to apache 2.4
Date: Thu, 09 Apr 2015 11:33:23 +0200 [thread overview]
Message-ID: <55264763.6050703@drmicha.warpmail.net> (raw)
In-Reply-To: <20150408202615.GA12154@dcvr.yhbt.net>
Eric Wong venit, vidit, dixit 08.04.2015 22:26:
> Michael J Gruber <git@drmicha.warpmail.net> wrote:
>> The current config is tailored to apache 2.2. Apache 2.4 fails to start
>> with it.
>>
>> Adjust the config to apache 2.4.
>>
>> Signed-off-by: Michael J Gruber <git@drmicha.warpmail.net>
>> ---
>
> 1/3 and 2/3 tested fine on Debian stable (wheezy).
> You can add my Tested-by to 1/3 and my S-o-b to 2/3.
Thanks, that's good to know.
> ...but not this one.
>
>> Notes:
>> This is WIP and RFH. Apache does not start without mpm, and the lock
>> mechanism has changed. It will run with these changes, but svn fails to
>> connect.
>>
>> Again, I'm wondering who is running these tests at all, but also:
>> Why do we leverage lib-httpd so little from lib-git-svn?
>
> I'm only testing on Apache 2.2 (from Debian stable (wheezy)).
So debian stable has apache 2.2? That explains why many don't see these
problems.
> I doubt anybody here, myself included, likes dealing with SVN,
> and would rather ignore the tests than try to fix them.
>
> lib-git-svn predates lib-httpd, and it isn't very interesting work
> to port and cleanup.
I agree with everything above. But if (and that's a big if) the tests
don't run for anyone I'd rather remove them if there's no way to port them.
>> +LoadModule mpm_prefork_module $SVN_HTTPD_MODULE_PATH/mod_mpm_prefork.so
>
> I think you need an IfModule guard around this?
>
> I have no mod_mpm_prefork.so file with the apache2-mpm-prefork
> (2.2.22-13+deb7u4) package on Debian wheezy.
Sure, the changes in 3/3 are for apache 2.4 only and should be guarded
by a version check the same way as the ones in lib-httpd.
I'm just trying to figure out how to run them at all first.
So, before 3/3, t9118 and such do run the web server and test git-svn
against that for you?
Michael
next prev parent reply other threads:[~2015-04-09 9:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-08 15:05 [PATCH 0/3] Make httpd tests run Michael J Gruber
2015-04-08 15:05 ` [PATCH 1/3] t/lib-httpd: load mod_unixd Michael J Gruber
[not found] ` <5525A208.6060807@web.de>
2015-04-09 9:27 ` Michael J Gruber
2015-04-10 3:09 ` Jeff King
2015-04-08 15:05 ` [PATCH 2/3] t/lib-git-svn: check same httpd module dirs as lib-httpd Michael J Gruber
2015-04-08 15:05 ` [WIP/RFH/PATCH 3/3] t/lib-git-svn: adjust config to apache 2.4 Michael J Gruber
2015-04-08 20:26 ` Eric Wong
2015-04-09 9:33 ` Michael J Gruber [this message]
2015-04-09 19:11 ` Eric Wong
2015-04-10 3:23 ` Jeff King
2015-04-10 3:39 ` Jeff King
2015-04-13 10:14 ` Michael J Gruber
2015-04-09 13:04 ` [PATCH 0/3] Make httpd tests run Kyle J. McKay
2015-04-09 13:14 ` Kyle J. McKay
2015-05-11 11:54 ` [PATCHv2 0/4] Make httpd tests run v2 Michael J Gruber
2015-05-11 11:54 ` [PATCHv2 1/4] t/lib-httpd: load mod_unixd Michael J Gruber
2015-05-11 11:54 ` [PATCHv2 2/4] t/lib-git-svn: check same httpd module dirs as lib-httpd Michael J Gruber
2015-05-11 11:54 ` [PATCH 3/4] t/t91*: do not say how to avoid the tests Michael J Gruber
2015-05-11 11:54 ` [PATCHv2 4/4 (was 3/3, still WIP)] t/lib-git-svn: adjust config to apache 2.4 WIP Michael J Gruber
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55264763.6050703@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=normalperson@yhbt.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).