Bug#350822: marked as done (apache2-doc: add Readme on how to browse the docs)

Your message dated Sun, 01 Jul 2007 19:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#350822: fixed in apache2 2.2.4-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

Bug#305933: marked as done (move conf.d include in apache2.conf)

Your message dated Sun, 01 Jul 2007 19:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#305933: fixed in apache2 2.2.4-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

Bug#431125: marked as done (apache2.2-common: shouldn't depend on procps on the Hurd)

Your message dated Sun, 01 Jul 2007 19:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#431125: fixed in apache2 2.2.4-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

Bug#291841: marked as done (Wrong/unnecessary directory/file permissions /var/log/apache2)

Your message dated Sun, 01 Jul 2007 19:02:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#291841: fixed in apache2 2.2.4-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

Bug#414429: marked as done (apache2-doc: say how to read the manual but fix charset first)

Your message dated Sun, 01 Jul 2007 19:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#414429: fixed in apache2 2.2.4-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

Bug#368109: marked as done (apache2-common: Move the Include /etc/apache2/conf.d/[^.#]* to the end)

Your message dated Sun, 01 Jul 2007 19:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#305933: fixed in apache2 2.2.4-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

Bug#334824: marked as done (logrotate: Postrotate documentation - Why restart?)

Your message dated Sun, 01 Jul 2007 19:02:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#298689: fixed in apache2 2.2.4-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

Bug#398223: marked as done (apache2: "[notice] caught SIGTERM, shutting down")

Your message dated Sun, 01 Jul 2007 19:02:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#298689: fixed in apache2 2.2.4-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

Bug#298689: marked as done (apache2: logrotate script and new init script break ssl certificates with passphrase)

Your message dated Sun, 01 Jul 2007 19:02:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#298689: fixed in apache2 2.2.4-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

Bug#419539: marked as done (options error in Apache config file)

Your message dated Sun, 01 Jul 2007 19:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#419539: fixed in apache2 2.2.4-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

Bug#399056: marked as done (apache2 could suggest apache2-doc and www-browser as apache2-common did)

Your message dated Sun, 01 Jul 2007 19:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#399056: fixed in apache2 2.2.4-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

Bug#427050: marked as done (apache2: New upstream: 2.2.4)

Your message dated Sun, 01 Jul 2007 19:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#427050: fixed in apache2 2.2.4-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

Bug#408429: marked as done (apache2-doc: say how to browse manual)

Your message dated Sun, 01 Jul 2007 19:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#350822: fixed in apache2 2.2.4-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

Bug#289289: marked as done (apache2-doc: needed /etc/init.d/apache2 restart to get the http://localhost/manual/ working)

Your message dated Sun, 01 Jul 2007 19:02:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#289289: fixed in apache2 2.2.4-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

Bug#428887: marked as done (apache2.2-common: files left upon purge)

Your message dated Sun, 01 Jul 2007 19:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#428887: fixed in apache2 2.2.4-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

Bug#430116: marked as done (apache2.2-common: /etc/init.d/apache2 start does nothing)

Your message dated Sun, 01 Jul 2007 19:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#430116: fixed in apache2 2.2.4-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

Bug#384682: marked as done (init.d restart fails if previous start failed)

Your message dated Sun, 01 Jul 2007 19:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#384682: fixed in apache2 2.2.4-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

Bug#410331: marked as done ("proxy: error reading status line from remote server" using Apache2 mod_proxy against IIS)

Your message dated Sun, 01 Jul 2007 19:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#410331: fixed in apache2 2.2.4-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

Bug#425248: marked as done (apache2.2-common: apache2 may be killed by logrotate job)

Your message dated Sun, 01 Jul 2007 19:02:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#298689: fixed in apache2 2.2.4-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

Bug#400455: marked as done (apache2.2-common: "/etc/init.d/apache2 restart" can kill apache)

Your message dated Sun, 01 Jul 2007 19:02:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#298689: fixed in apache2 2.2.4-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

Bug#415698: marked as done (apache2.2-common: does not create /usr/lib/cgi-bin common anymore.)

Your message dated Sun, 01 Jul 2007 19:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#415698: fixed in apache2 2.2.4-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

Bug#391817: marked as done (apache2-mpm-prefork: /usr/sbin/apache2 -h doesn't list the -X option)

Your message dated Sun, 01 Jul 2007 19:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#391817: fixed in apache2 2.2.4-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

Bug#429516: marked as done (apache2-common & logrotate : could reload be used instead of restart ?)

Your message dated Sun, 01 Jul 2007 19:02:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#298689: fixed in apache2 2.2.4-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

Bug#325594: marked as done (apache2: Unable to restart after security upgrade)

Your message dated Sun, 01 Jul 2007 19:02:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#298689: fixed in apache2 2.2.4-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

Bug#314878: marked as done (apache2-common: Do 'reload' instead of 'restart' in logrotate.d/apache2)

Your message dated Sun, 01 Jul 2007 19:02:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#298689: fixed in apache2 2.2.4-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

Bug#431048: marked as done (suexec permissions are DANGEROUS)

Your message dated Sun, 01 Jul 2007 19:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#431048: fixed in apache2 2.2.4-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

Bug#418536: marked as done (apache2 can't be removed if stoppped)

Your message dated Sun, 01 Jul 2007 19:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#418536: fixed in apache2 2.2.4-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

Bug#412580: marked as done (Apache reporting incorrect header values for error 500 documents)

Your message dated Sun, 01 Jul 2007 19:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#412580: fixed in apache2 2.2.4-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

Bug#301702: marked as done (apache2 start failed during restart when logs rotated)

Your message dated Sun, 01 Jul 2007 19:02:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#298689: fixed in apache2 2.2.4-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

Bug#350286: marked as done (apache2-common: why is the apache2 pid file not in /var/run/apache2?)

Your message dated Sun, 01 Jul 2007 19:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#350286: fixed in apache2 2.2.4-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

Bug#404558: marked as done (apache2.conf has Include in wrong place)

Your message dated Sun, 01 Jul 2007 19:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#305933: fixed in apache2 2.2.4-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

apache2_2.2.4-1_i386.changes ACCEPTED

Accepted: apache2-doc_2.2.4-1_all.deb to pool/main/a/apache2/apache2-doc_2.2.4-1_all.deb apache2-mpm-event_2.2.4-1_i386.deb to pool/main/a/apache2/apache2-mpm-event_2.2.4-1_i386.deb apache2-mpm-perchild_2.2.4-1_all.deb to pool/main/a/apache2/apache2-mpm-perchild_2.2.4-1_all.deb apache2-mpm-p

apache2 override disparity

There are disparities between your recently accepted upload and the override file for the following file(s): apache2-mpm-event_2.2.4-1_i386.deb: package says section is web, override says net. apache2-mpm-perchild_2.2.4-1_all.deb: package says section is web, override says net. apache2-mpm-prefo

Processing of apache2_2.2.4-1_i386.changes

apache2_2.2.4-1_i386.changes uploaded successfully to localhost along with the files: apache2_2.2.4-1.dsc apache2_2.2.4.orig.tar.gz apache2_2.2.4-1.diff.gz apache2.2-common_2.2.4-1_i386.deb apache2-mpm-worker_2.2.4-1_i386.deb apache2-mpm-prefork_2.2.4-1_i386.deb apache2-mpm-event_2.2.