On Mon, 27 Oct 2003 14:05:29 +, chbaker wrote:
> BTW, was someone suggesting that I should read the bug reports for every
> package before going ahead with an ``apt-get -u dist-upgrade''. I suppose
> if I were really cautious I would, but then I wouldn't be running unstable
> would I ;-) Thank
link.net>cc:
Subject: Re: apache 1.3.28-4 on
unstable
10/25/2003 11:20
On Saturday 25 October 2003 10:05 pm, W. Paul Mills wrote:
>>>Well, it is a known bug in the apache package, you should have checked.
>>>The basic problem is that the modules are inserted into modules.conf in
>>>reverse order.
>>>
Ouch, this just bit me too. Editing modules.conf didn't seem to
>>Well, it is a known bug in the apache package, you should have checked.
>>The basic problem is that the modules are inserted into modules.conf in
>>reverse order.
>
>>>Ouch, this just bit me too. Editing modules.conf didn't seem to work
>>>What's a fix?
For some reason I never saw this messag
On Friday 24 October 2003 9:55 pm, W. Paul Mills wrote:
>On Fri, 24 Oct 2003 20:45:46 +, chbaker wrote:
>> Ever since upgrading to apache 1.3.28-4 on unstable some strange things
>> have happened. Index pages, whether html, shtml, or cgi are no longer
>> working unless the page is explicitly li
On Friday 24 October 2003 9:55 pm, W. Paul Mills wrote:
>On Fri, 24 Oct 2003 20:45:46 +, chbaker wrote:
>> Ever since upgrading to apache 1.3.28-4 on unstable some strange things
>> have happened. Index pages, whether html, shtml, or cgi are no longer
>> working unless the page is explicitly li
On Fri, 24 Oct 2003 20:45:46 +, chbaker wrote:
> Ever since upgrading to apache 1.3.28-4 on unstable some strange things
> have happened. Index pages, whether html, shtml, or cgi are no longer
> working unless the page is explicitly listed. Example
> ``http://servername/'' yeilds a 403 Forbidd
7 matches
Mail list logo
