Accepted:
apache2-common_2.0.55-2_i386.deb
to pool/main/a/apache2/apache2-common_2.0.55-2_i386.deb
apache2-doc_2.0.55-2_all.deb
to pool/main/a/apache2/apache2-doc_2.0.55-2_all.deb
apache2-mpm-perchild_2.0.55-2_i386.deb
to pool/main/a/apache2/apache2-mpm-perchild_2.0.55-2_i386.deb
apache2-mpm
Your message dated Sat, 22 Oct 2005 22:02:08 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#311317: fixed in apache2 2.0.55-2
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 y
Your message dated Sat, 22 Oct 2005 22:02:08 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#316477: fixed in apache2 2.0.55-2
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 y
Your message dated Sat, 22 Oct 2005 22:02:08 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#332619: fixed in apache2 2.0.55-2
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 y
Your message dated Sat, 22 Oct 2005 22:02:08 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#251800: fixed in apache2 2.0.55-2
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 y
Your message dated Sat, 22 Oct 2005 22:02:08 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#307665: fixed in apache2 2.0.55-2
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 y
apache2_2.0.55-2_i386.changes uploaded successfully to localhost
along with the files:
apache2_2.0.55-2.dsc
apache2_2.0.55-2.diff.gz
apache2-doc_2.0.55-2_all.deb
apache2-common_2.0.55-2_i386.deb
apache2-utils_2.0.55-2_i386.deb
apache2-mpm-worker_2.0.55-2_i386.deb
apache2-mpm-perchild_
Your message dated Sat, 22 Oct 2005 18:47:11 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#63: fixed in apache2 2.0.55-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 y
Your message dated Sat, 22 Oct 2005 18:47:07 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#334336: fixed in apache 1.3.34-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 yo
Your message dated Sat, 22 Oct 2005 18:47:11 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#332791: fixed in apache2 2.0.55-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 y
Your message dated Sat, 22 Oct 2005 18:47:11 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#331741: fixed in apache2 2.0.55-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 y
Your message dated Sat, 22 Oct 2005 18:47:07 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#321824: fixed in apache 1.3.34-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 yo
Your message dated Sat, 22 Oct 2005 18:47:11 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#327269: fixed in apache2 2.0.55-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 y
Your message dated Sat, 22 Oct 2005 18:47:07 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#328212: fixed in apache 1.3.34-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 yo
Your message dated Sat, 22 Oct 2005 18:47:07 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#316642: fixed in apache 1.3.34-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 yo
Your message dated Sat, 22 Oct 2005 18:47:11 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#316303: fixed in apache2 2.0.55-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 y
Your message dated Sat, 22 Oct 2005 18:47:11 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#303076: fixed in apache2 2.0.55-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 y
Your message dated Sat, 22 Oct 2005 18:47:07 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#281379: fixed in apache 1.3.34-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 yo
Accepted:
apache-common_1.3.34-1_i386.deb
to pool/main/a/apache/apache-common_1.3.34-1_i386.deb
apache-dbg_1.3.34-1_i386.deb
to pool/main/a/apache/apache-dbg_1.3.34-1_i386.deb
apache-dev_1.3.34-1_all.deb
to pool/main/a/apache/apache-dev_1.3.34-1_all.deb
apache-doc_1.3.34-1_all.deb
to pool/
Accepted:
apache2-common_2.0.55-1_i386.deb
to pool/main/a/apache2/apache2-common_2.0.55-1_i386.deb
apache2-doc_2.0.55-1_all.deb
to pool/main/a/apache2/apache2-doc_2.0.55-1_all.deb
apache2-mpm-perchild_2.0.55-1_i386.deb
to pool/main/a/apache2/apache2-mpm-perchild_2.0.55-1_i386.deb
apache2-mpm
apache_1.3.34-1_i386.changes uploaded successfully to localhost
along with the files:
apache_1.3.34-1.dsc
apache_1.3.34.orig.tar.gz
apache_1.3.34-1.diff.gz
apache-doc_1.3.34-1_all.deb
apache-dev_1.3.34-1_all.deb
apache_1.3.34-1_i386.deb
apache-ssl_1.3.34-1_i386.deb
apache-perl_1.3.3
apache2_2.0.55-1_i386.changes uploaded successfully to localhost
along with the files:
apache2_2.0.55-1.dsc
apache2_2.0.55.orig.tar.gz
apache2_2.0.55-1.diff.gz
apache2-doc_2.0.55-1_all.deb
apache2-common_2.0.55-1_i386.deb
apache2-utils_2.0.55-1_i386.deb
apache2-mpm-worker_2.0.55-1_i38
Member-Dallago
Profit-Picks Alert This Week: ANDL
ANDL is our hot pick this weekend it is a brand
new public company that is making money and
is on the move. So be aware of this alert and
we recommend this company highly be sure to
get in early there is a large campaign going over
the weeken
Your message dated Sun, 23 Oct 2005 06:27:55 +1000
with message-id <[EMAIL PROTECTED]>
and subject line Closing bug
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 responsibility to reop
My local partial debian mirror has had this problem many times, and
restarting apache fixes it for a while.
--
Blars Blarson [EMAIL PROTECTED]
http://www.blars.org/blars.html
With Microsoft, failure is not an option. It is a standard feature.
-
25 matches
Mail list logo