git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael J Gruber <git@drmicha.warpmail.net>
To: "Torsten Bögershausen" <tboegi@web.de>,
	"Git Mailing List" <git@vger.kernel.org>
Subject: Re: [PATCH 1/3] t/lib-httpd: load mod_unixd
Date: Thu, 09 Apr 2015 11:27:49 +0200	[thread overview]
Message-ID: <55264615.2050107@drmicha.warpmail.net> (raw)
In-Reply-To: <5525A208.6060807@web.de>

Torsten Bögershausen venit, vidit, dixit 08.04.2015 23:47:
> On 2015-04-08 17.05, Michael J Gruber wrote:
>> With the current config, apache 2.4.10 will not be started and the httpd
>> tests will not run.
>>
>> Enable mod_unixd to make the httpd tests run.
>>
>> Signed-off-by: Michael J Gruber <git@drmicha.warpmail.net>
>> ---
>>
>> Notes:
>>     Basically, this is required since the switch from 2.2 to 2.4.
>>     I'm wondering whether noone is running these tests, or other
>>     distros (than Fedora) use different default configs.
> Do you have any special test numbers in mind  ?
> The following are running under Debian:
> 
> *** t5541-http-push-smart.sh ***
> *** t5542-push-http-shallow.sh ***
> *** t5550-http-fetch-dumb.sh ***
> *** t5551-http-fetch-smart.sh ***
> *** t5560-http-backend-noserver.sh ***
> 
> (Then I stopped digging)
> 
> And this under Mac OS, 
> *** t5541-http-push-smart.sh ***
> You do not seem to have gpg installed
> ok 1 - setup remote repository
> ....

Is this with apache 2.4?

In my case (apache 2.4, fedora 21), t/lib-http.sh failed to start the
web server, so the tests above would (succeed trivially but) not run.

Maybe debian is using an apache default config that has mod_unixd built
in, to ease the transition from apache 2.2? Many were bitten by these
new requirements after the switch to 2.4, and some distros may have
worked around that.

Do your tests run with this patch applied?

Michael

  parent reply	other threads:[~2015-04-09  9:28 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 [this message]
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
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=55264615.2050107@drmicha.warpmail.net \
    --to=git@drmicha.warpmail.net \
    --cc=git@vger.kernel.org \
    --cc=tboegi@web.de \
    /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).