Re: apache 1.3.29.0.1-4 and -5

2004-01-27 Thread Jeroen van Wolffelaar
(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

Bug#230016: apache: fails to install if /bin/sh - dash

2004-01-27 Thread Domenico Andreoli
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

Apache 2.0.48 still not in testing

2004-01-27 Thread Alessandro Polverini
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

apache_1.3.29.0.1-4_i386.changes ACCEPTED

2004-01-27 Thread Debian Installer
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

Bug#229728: marked as done (Nicer output upon apache start)

2004-01-27 Thread Debian Bug Tracking System
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

Bug#229553: marked as done (debconf note spam)

2004-01-27 Thread Debian Bug Tracking System
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

Bug#228667: marked as done (apache: fails to start after fresh install)

2004-01-27 Thread Debian Bug Tracking System
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

Bug#228033: marked as done (apache does not start)

2004-01-27 Thread Debian Bug Tracking System
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

Bug#227997: marked as done (mod_usertrack causes segfault)

2004-01-27 Thread Debian Bug Tracking System
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

Bug#225634: marked as done (apache, apache-perl, apache-ssl cannot run from inetd when including a directory as config source.)

2004-01-27 Thread Debian Bug Tracking System
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

Bug#225047: marked as done (libapache-mod-perl: Error in post install script - no such file or directory)

2004-01-27 Thread Debian Bug Tracking System
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

Bug#227357: marked as done (/usr/lib/apache/1.3/mod_log_config.so undefined symbol: ap_popenf_ex (from log rotate?); but it obviously can...)

2004-01-27 Thread Debian Bug Tracking System
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

Bug#225015: marked as done (apache: fails to upgrade)

2004-01-27 Thread Debian Bug Tracking System
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

Bug#224390: marked as done (apache-ssl: SSLCacheServerPort: httpd.conf not updated)

2004-01-27 Thread Debian Bug Tracking System
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

Bug#225608: marked as done (apache-ssl: post-installation script fails on upgrade (during --configure))

2004-01-27 Thread Debian Bug Tracking System
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

Bug#228451: marked as done (apache-dev: could you upgrade to libdb4.2-dev dependency , 4.1 conflict with gnome-dev)

2004-01-27 Thread Debian Bug Tracking System
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

Bug#228946: marked as done (apache: apache 1.3.29.0.1-3 conflicts with libapache-mod-perl 1.27, causing coredumps)

2004-01-27 Thread Debian Bug Tracking System
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

Bug#230038: apache-common: Bashism in /usr/share/apache/postinst.common causes upgrade failure

2004-01-27 Thread Michael Gurski
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