Your message dated Thu, 11 Dec 2003 11:18:04 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#170854: fixed in apache 1.3.29.0.1-1
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 no
Your message dated Thu, 11 Dec 2003 11:18:04 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#104268: fixed in apache 1.3.29.0.1-1
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 no
Your message dated Thu, 11 Dec 2003 11:18:04 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#136634: fixed in apache 1.3.29.0.1-1
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 no
Your message dated Thu, 11 Dec 2003 11:18:04 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#144644: fixed in apache 1.3.29.0.1-1
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 no
Your message dated Thu, 11 Dec 2003 11:18:05 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#89484: fixed in apache 1.3.29.0.1-1
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 now
Your message dated Thu, 11 Dec 2003 11:18:04 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#153528: fixed in apache 1.3.29.0.1-1
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 no
Your message dated Thu, 11 Dec 2003 11:18:04 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#172527: fixed in apache 1.3.29.0.1-1
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 no
Your message dated Thu, 11 Dec 2003 11:18:05 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#218119: fixed in apache 1.3.29.0.1-1
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 no
Your message dated Thu, 11 Dec 2003 11:18:04 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#109460: fixed in apache 1.3.29.0.1-1
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 no
Your message dated Thu, 11 Dec 2003 11:18:05 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#221138: fixed in apache 1.3.29.0.1-1
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 no
Your message dated Thu, 11 Dec 2003 11:18:05 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#192489: fixed in apache 1.3.29.0.1-1
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 no
Your message dated Thu, 11 Dec 2003 11:18:05 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#192489: fixed in apache 1.3.29.0.1-1
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 no
Your message dated Thu, 11 Dec 2003 11:18:05 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#221138: fixed in apache 1.3.29.0.1-1
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 no
Your message dated Thu, 11 Dec 2003 11:18:05 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#221138: fixed in apache 1.3.29.0.1-1
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 no
Your message dated Thu, 11 Dec 2003 11:18:05 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#215904: fixed in apache 1.3.29.0.1-1
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 no
Your message dated Thu, 11 Dec 2003 11:18:05 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#220041: fixed in apache 1.3.29.0.1-1
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 no
Your message dated Thu, 11 Dec 2003 11:18:05 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#220041: fixed in apache 1.3.29.0.1-1
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 no
Accepted:
apache-common_1.3.29.0.1-1_i386.deb
to pool/main/a/apache/apache-common_1.3.29.0.1-1_i386.deb
apache-dbg_1.3.29.0.1-1_i386.deb
to pool/main/a/apache/apache-dbg_1.3.29.0.1-1_i386.deb
apache-dev_1.3.29.0.1-1_i386.deb
to pool/main/a/apache/apache-dev_1.3.29.0.1-1_i386.deb
apache-doc_1
apache_1.3.29.0.1-1_i386.changes uploaded successfully to localhost
along with the files:
apache_1.3.29.0.1-1.dsc
apache_1.3.29.0.1.orig.tar.gz
apache_1.3.29.0.1-1.diff.gz
apache-doc_1.3.29.0.1-1_all.deb
apache_1.3.29.0.1-1_i386.deb
apache-ssl_1.3.29.0.1-1_i386.deb
apache-perl_1.3.29.
This is actually a problem with update-rc.d. If you check in the man page
update-rc.d does not change the links if there are some already in order
to preserve user changes. The same goes for bind9. If you check the
postinst for bind9 you will notice that it is configured to start at 15
but your li
On Thu, Dec 11, 2003 at 07:43:29AM +0100, Florian Weimer wrote:
> In the default configuration, web servers shall bind to localhost only
> (okay, that's are more general policy issue affecting all network
> services).
um, that's a completely separate Policy proposal; i don't think it helps
anyone
Processing commands for [EMAIL PROTECTED]:
> severity 223576 important
Bug#223576: libapache-mod-python: hangs in modules-config
Severity set to `important'.
> tags 223576 + pending
Bug#223576: libapache-mod-python: hangs in modules-config
Tags were: sid
Tags added: pending
> merge 223576 221133
Gushing Holes!
Intense Female Ejaculations
Experience the 3 foot 0rgasm (that 0 is a zero)
http://www.blindfantasy.com/guer_ads/dmail.php?grid=84&ape=gt1609
You have to see it to believe it!
Don't get hit in the eye
http://www.blindfantasy.com/guer_ads/dmail.php?grid=84&ape=gt1609
http://nonde
The problems are 2.
1) we were calling a db_stop too much that was not required
2) apache* on restart uses fd=3 that is used by debconf and the debconf
frontend. (known problem of debconf here).
for the first we removed the db_stop call, for the second we had to
nullify the output of apache* res
Joey Hess wrote:
> - Any others?
In the default configuration, web servers shall bind to localhost only
(okay, that's are more general policy issue affecting all network
services).
26 matches
Mail list logo
