apache2_2.2.3-5_i386.changes uploaded successfully to localhost
along with the files:
apache2_2.2.3-5.dsc
apache2_2.2.3-5.diff.gz
apache2.2-common_2.2.3-5_i386.deb
apache2-mpm-worker_2.2.3-5_i386.deb
apache2-mpm-prefork_2.2.3-5_i386.deb
apache2-mpm-event_2.2.3-5_i386.deb
Your message dated Sun, 10 Jun 2007 17:47:04 +
with message-id [EMAIL PROTECTED]
and subject line Bug#396162: fixed in apache2 2.2.3-5
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 Sun, 10 Jun 2007 17:47:04 +
with message-id [EMAIL PROTECTED]
and subject line Bug#419552: fixed in apache2 2.2.3-5
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 Sun, 10 Jun 2007 17:47:04 +
with message-id [EMAIL PROTECTED]
and subject line Bug#428058: fixed in apache2 2.2.3-5
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 Sun, 10 Jun 2007 17:47:04 +
with message-id [EMAIL PROTECTED]
and subject line Bug#420101: fixed in apache2 2.2.3-5
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 Sun, 10 Jun 2007 17:47:04 +
with message-id [EMAIL PROTECTED]
and subject line Bug#312385: fixed in apache2 2.2.3-5
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 Sun, 10 Jun 2007 17:47:04 +
with message-id [EMAIL PROTECTED]
and subject line Bug#390348: fixed in apache2 2.2.3-5
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 Sun, 10 Jun 2007 17:47:04 +
with message-id [EMAIL PROTECTED]
and subject line Bug#423653: fixed in apache2 2.2.3-5
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 Sun, 10 Jun 2007 17:47:04 +
with message-id [EMAIL PROTECTED]
and subject line Bug#416322: fixed in apache2 2.2.3-5
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 Sun, 10 Jun 2007 17:47:04 +
with message-id [EMAIL PROTECTED]
and subject line Bug#412580: fixed in apache2 2.2.3-5
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
There are disparities between your recently accepted upload and the
override file for the following file(s):
apache2-mpm-event_2.2.3-5_i386.deb: package says section is web, override says
net.
apache2-mpm-perchild_2.2.3-5_all.deb: package says section is web, override
says net.
Accepted:
apache2-doc_2.2.3-5_all.deb
to pool/main/a/apache2/apache2-doc_2.2.3-5_all.deb
apache2-mpm-event_2.2.3-5_i386.deb
to pool/main/a/apache2/apache2-mpm-event_2.2.3-5_i386.deb
apache2-mpm-perchild_2.2.3-5_all.deb
to pool/main/a/apache2/apache2-mpm-perchild_2.2.3-5_all.deb
Your message dated Sun, 10 Jun 2007 17:47:04 +
with message-id [EMAIL PROTECTED]
and subject line Bug#400981: fixed in apache2 2.2.3-5
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 Sun, 10 Jun 2007 17:47:04 +
with message-id [EMAIL PROTECTED]
and subject line Bug#403682: fixed in apache2 2.2.3-5
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 Sun, 10 Jun 2007 17:47:04 +
with message-id [EMAIL PROTECTED]
and subject line Bug#422589: fixed in apache2 2.2.3-5
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 Sun, 10 Jun 2007 17:47:04 +
with message-id [EMAIL PROTECTED]
and subject line Bug#401053: fixed in apache2 2.2.3-5
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 Sun, 10 Jun 2007 17:47:04 +
with message-id [EMAIL PROTECTED]
and subject line Bug#391813: fixed in apache2 2.2.3-5
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 Sun, 10 Jun 2007 17:47:04 +
with message-id [EMAIL PROTECTED]
and subject line Bug#399043: fixed in apache2 2.2.3-5
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 Sun, 10 Jun 2007 17:47:04 +
with message-id [EMAIL PROTECTED]
and subject line Bug#420101: fixed in apache2 2.2.3-5
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 Sun, 10 Jun 2007 17:47:04 +
with message-id [EMAIL PROTECTED]
and subject line Bug#322385: fixed in apache2 2.2.3-5
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 Sun, 10 Jun 2007 17:47:04 +
with message-id [EMAIL PROTECTED]
and subject line Bug#412407: fixed in apache2 2.2.3-5
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 Sun, 10 Jun 2007 17:47:04 +
with message-id [EMAIL PROTECTED]
and subject line Bug#322385: fixed in apache2 2.2.3-5
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 Sun, 10 Jun 2007 17:47:04 +
with message-id [EMAIL PROTECTED]
and subject line Bug#322385: fixed in apache2 2.2.3-5
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 Sun, 10 Jun 2007 17:47:04 +
with message-id [EMAIL PROTECTED]
and subject line Bug#397789: fixed in apache2 2.2.3-5
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 Sun, 10 Jun 2007 17:47:04 +
with message-id [EMAIL PROTECTED]
and subject line Bug#397789: fixed in apache2 2.2.3-5
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 Sun, 10 Jun 2007 17:47:04 +
with message-id [EMAIL PROTECTED]
and subject line Bug#412602: fixed in apache2 2.2.3-5
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 Sun, 10 Jun 2007 17:47:04 +
with message-id [EMAIL PROTECTED]
and subject line Bug#407307: fixed in apache2 2.2.3-5
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 Sun, 10 Jun 2007 17:47:04 +
with message-id [EMAIL PROTECTED]
and subject line Bug#413727: fixed in apache2 2.2.3-5
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 Sun, 10 Jun 2007 17:47:04 +
with message-id [EMAIL PROTECTED]
and subject line Bug#418464: fixed in apache2 2.2.3-5
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
I can't tell for sure whether Stefan's comment (posted today) means the
intent is that the patch posted by Tim on the 28th will be applied, or
if the latest version of Apache will really be used. I want to assume
the latter, based on the phrase the latest version of apache2 ... but
I thought
30 matches
Mail list logo
