Hi.
Just wanted to point out that as a workaround running as root worked for
me (on debian stretch using cpan2deb).
Sincerely,
Joachim
--
Papier ist gebundenes CO2. Bitte drucken Sie diese EMail aus und archivieren
Sie sie.
On Fri, Mar 10, 2017 at 1:51 PM, Sam Tregar wrote:
>
> I think this could be fixed by just the part of my patch that allowed for
> IncludeOptional in addition to Include when finding sub-confs for inheriting
> the parts that load an MPM. I'll work up a patch that switches to
Thanks - it wasn't clear to me which comments earlier were from maintainers
and which from interested bystanders. No patch will ever be universally
loved, so I thought I'd try to figure out which changes needed to be made.
Sam
On Thu, Mar 9, 2017 at 2:26 PM, William A Rowe Jr
No it does not. Ubuntu and Debian still error:
waiting 60 seconds for server to start: .AH00534: apache2: Configuration
error: No MPM loaded.
I think this could be fixed by just the part of my patch that allowed for
IncludeOptional in addition to Include when finding sub-confs for
inheriting
On Thu, Mar 9, 2017 at 3:23 PM, Sam Tregar wrote:
> I'm not totally clear on who's maintaining Apache::Test.
>
> If not, what changes would you need to take it?
Refer back to my earlier comments. There is very little chance that any
specific vendor deviations will be
On Thu, Mar 9, 2017 at 4:23 PM, Sam Tregar wrote:
> I'm not totally clear on who's maintaining Apache::Test. If you are the
> maintainer, can you say whether you'll take my patch to get the module
> working on Debian and Ubuntu? If not, what changes would you need to take
> it?
I'm not totally clear on who's maintaining Apache::Test. If you are the
maintainer, can you say whether you'll take my patch to get the module
working on Debian and Ubuntu? If not, what changes would you need to take
it?
Thanks!
Sam
On Tue, Mar 7, 2017 at 11:15 AM, William A Rowe Jr
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:
>
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
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
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
vars to set?
That file unsets HOME on Ubuntu and changes LANG to C, so if
That seems like a reasonable solution. Do you think we should switch to
using apachectl everywhere, or try to detect whether it's necessary?
Sam
On Mon, Mar 6, 2017 at 12:46 PM, Eric Covener wrote:
> On Mon, Mar 6, 2017 at 3:23 PM, Stefan Fritsch wrote:
On Mon, Mar 6, 2017 at 3:23 PM, Stefan Fritsch wrote:
> These are set in /etc/apache2/envvars. You should simply source that file
> before running the test suite. Also, you can pass another config file name to
> the test suite. Maybe this helps:
I can't remember/find the parm,
On Friday, 3 March 2017 22:59:10 CET Sam Tregar wrote:
> Hello all. I've been working on getting Apache::Test running on Debian and
> it's not going well. One problem seems to be that Debian's system Apache
> conf is not named what Apache::Test thinks it should be named (apache2.conf
> vs
I have attached a patch for this issue and a few others I found while
trying to run tests on recent Debian and Ubuntu servers. Please let me
know if you have any questions.
Part of this patch came from this Debian patch that seemingly hasn't gotten
back into the main distro:
Hello all. I've been working on getting Apache::Test running on Debian and
it's not going well. One problem seems to be that Debian's system Apache
conf is not named what Apache::Test thinks it should be named (apache2.conf
vs httpd.conf).
After solving that problem I hit a bigger one - the
20 matches
Mail list logo