(Still not on the list, so Cc please if you want feedback)
On Tue, Jan 27, 2004 at 01:03:52PM +0100, Fabio Massimo Di Nitto wrote:
Hi all,
we are close to upload -4 (probably today) that will NOT fix bug
227232 yet but other 18 bugs.
This uplaod is focused to provide a smooth
Package: apache
Version: 1.3.29.0.1-4
Severity: important
...
Do you want to continue? [Y/n]
Setting up apache (1.3.29.0.1-4) ...
/var/lib/dpkg/info/apache.postinst: 40: cannot open
/etc/apache/httpd.conf/etc/apache/modules.conf: No such file
/var/lib/dpkg/info/apache.postinst: 40: cannot open
Hello,
it's now more than 71 days that the latest release of apache is stuck in
sid and does not enter testing.
Looking at the critical bug reports, the only one I find is applicable
also to apache 2.0.47 which is already in testing.
Of course having apache2 multi threaded in Sarge would be
Accepted:
apache-common_1.3.29.0.1-4_i386.deb
to pool/main/a/apache/apache-common_1.3.29.0.1-4_i386.deb
apache-dbg_1.3.29.0.1-4_i386.deb
to pool/main/a/apache/apache-dbg_1.3.29.0.1-4_i386.deb
apache-dev_1.3.29.0.1-4_i386.deb
to pool/main/a/apache/apache-dev_1.3.29.0.1-4_i386.deb
Your message dated Tue, 27 Jan 2004 13:04:51 -0500
with message-id [EMAIL PROTECTED]
and subject line Bug#229728: fixed in apache 1.3.29.0.1-4
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 Tue, 27 Jan 2004 13:04:40 -0500
with message-id [EMAIL PROTECTED]
and subject line Bug#229027: fixed in apache 1.3.29.0.1-4
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 Tue, 27 Jan 2004 13:03:39 -0500
with message-id [EMAIL PROTECTED]
and subject line Bug#228033: fixed in apache 1.3.29.0.1-4
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 Tue, 27 Jan 2004 13:03:39 -0500
with message-id [EMAIL PROTECTED]
and subject line Bug#228033: fixed in apache 1.3.29.0.1-4
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 Tue, 27 Jan 2004 13:03:35 -0500
with message-id [EMAIL PROTECTED]
and subject line Bug#227997: fixed in apache 1.3.29.0.1-4
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 Tue, 27 Jan 2004 13:03:08 -0500
with message-id [EMAIL PROTECTED]
and subject line Bug#225634: fixed in apache 1.3.29.0.1-4
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 Tue, 27 Jan 2004 13:02:47 -0500
with message-id [EMAIL PROTECTED]
and subject line Bug#225047: fixed in apache 1.3.29.0.1-4
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 Tue, 27 Jan 2004 13:02:44 -0500
with message-id [EMAIL PROTECTED]
and subject line Bug#225015: fixed in apache 1.3.29.0.1-4
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 Tue, 27 Jan 2004 13:02:44 -0500
with message-id [EMAIL PROTECTED]
and subject line Bug#225015: fixed in apache 1.3.29.0.1-4
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 Tue, 27 Jan 2004 13:02:36 -0500
with message-id [EMAIL PROTECTED]
and subject line Bug#224390: fixed in apache 1.3.29.0.1-4
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 Tue, 27 Jan 2004 13:02:57 -0500
with message-id [EMAIL PROTECTED]
and subject line Bug#225608: fixed in apache 1.3.29.0.1-4
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 Tue, 27 Jan 2004 13:03:59 -0500
with message-id [EMAIL PROTECTED]
and subject line Bug#228451: fixed in apache 1.3.29.0.1-4
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 Tue, 27 Jan 2004 13:04:30 -0500
with message-id [EMAIL PROTECTED]
and subject line Bug#228946: fixed in apache 1.3.29.0.1-4
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
Package: apache-common
Version: 1.3.29.0.1-4
Severity: normal
Lines 37 and 145 of /usr/share/apache/postinst.common assumes that
printf understands \xNN escapes, which is true under bash, but fails
if /bin/sh is another POSIX-compliant Bourne shell replacement, in
this case dash. Changing lines
18 matches
Mail list logo