Accepted:
apache2-doc_2.2.3-4+etch1_all.deb
to pool/main/a/apache2/apache2-doc_2.2.3-4+etch1_all.deb
apache2-mpm-event_2.2.3-4+etch1_i386.deb
to pool/main/a/apache2/apache2-mpm-event_2.2.3-4+etch1_i386.deb
apache2-mpm-perchild_2.2.3-4+etch1_all.deb
to
Your message dated Tue, 19 Jun 2007 07:52:15 +
with message-id [EMAIL PROTECTED]
and subject line Bug#423653: fixed in apache2 2.2.3-4+etch1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is
Your message dated Tue, 19 Jun 2007 07:52:15 +
with message-id [EMAIL PROTECTED]
and subject line Bug#298689: fixed in apache2 2.2.3-4+etch1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is
Your message dated Tue, 19 Jun 2007 07:52:15 +
with message-id [EMAIL PROTECTED]
and subject line Bug#298689: fixed in apache2 2.2.3-4+etch1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is
Your message dated Tue, 19 Jun 2007 07:52:15 +
with message-id [EMAIL PROTECTED]
and subject line Bug#298689: fixed in apache2 2.2.3-4+etch1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is
Your message dated Tue, 19 Jun 2007 07:52:15 +
with message-id [EMAIL PROTECTED]
and subject line Bug#298689: fixed in apache2 2.2.3-4+etch1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is
Your message dated Tue, 19 Jun 2007 07:52:15 +
with message-id [EMAIL PROTECTED]
and subject line Bug#419552: fixed in apache2 2.2.3-4+etch1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is
Your message dated Tue, 19 Jun 2007 07:52:15 +
with message-id [EMAIL PROTECTED]
and subject line Bug#298689: fixed in apache2 2.2.3-4+etch1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is
Your message dated Tue, 19 Jun 2007 07:52:15 +
with message-id [EMAIL PROTECTED]
and subject line Bug#298689: fixed in apache2 2.2.3-4+etch1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is
Your message dated Tue, 19 Jun 2007 07:52:15 +
with message-id [EMAIL PROTECTED]
and subject line Bug#298689: fixed in apache2 2.2.3-4+etch1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is
Your message dated Tue, 19 Jun 2007 07:52:15 +
with message-id [EMAIL PROTECTED]
and subject line Bug#298689: fixed in apache2 2.2.3-4+etch1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is
Hi,
On Sun, 17 Jun 2007, Tony Houghton wrote:
The current version of apache2 won't run PHP files. It just sends the
source to the browser instead. I've checked all the config that I know
how to check. The php5.load and php5.conf files are correctly symlinked
from mods-available to mods-enabled
Processing commands for [EMAIL PROTECTED]:
# Automatically generated email from bts, devscripts version 2.9.26
retitle 409970 a2ensite/a2enmod need to check if an existing file/symlink in
sites-enabled is correct
Bug#409970: apache2: ignoring sites-enabled
Changed Bug title to
Maybe you created /etc/apache2/sites-enabled/ssl or copied something
there before doing a2ensite? In this case a2ensite will report that
the site is already enabled, and not enable the site.
a2dissite ssl
a2ensite ssl
should work (but look at /etc/apache2/sites-enabled/ssl first, as this
will
Processing commands for [EMAIL PROTECTED]:
#
# bts-link upstream status pull for source package apache2
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#
user [EMAIL PROTECTED]
Setting user to [EMAIL PROTECTED] (was [EMAIL PROTECTED]).
# remote status report for
In [EMAIL PROTECTED], you wrote:
On Sun, 17 Jun 2007, Tony Houghton wrote:
The current version of apache2 won't run PHP files. It just sends the
source to the browser instead. I've checked all the config that I know
how to check. The php5.load and php5.conf files are correctly symlinked
from
Your message dated Tue, 19 Jun 2007 14:39:52 +0200 (CEST)
with message-id [EMAIL PROTECTED]
and subject line Bug#429401: apache2: Doesn't execute PHP scripts
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the
On 6/17/07, Stefan Fritsch [EMAIL PROTECTED] wrote:
Hi,
On Sun, 17 Jun 2007, Antano Solar wrote:
The module negotiation.load is causing segmentation fault in apache2.
child pid 4660 exit signal Segmentation fault (11)
I can't reproduce that. Can you give some more information?
Does the
On Tue, 19 Jun 2007, Antano Solar wrote:
Yes it goes away when i move negotiation module outside the mods_enabled
dir.It happens on every request . The web page shows internal error. I am
using x86 on athlon 64 machine. The OS was an upgrade from etch(testing) -
lenny - sid.
What kind of page
19 matches
Mail list logo
