Bug#383267: apache: 383267: more info

I have this problem too. I modified /var/lib/dpkg/info/apache.* to include these lines at the very start: echo $* set -x The results were: # apt-get -f install Reading package lists... Done Building dependency tree... Done 0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded. 1 not

Bug#383267: postinst trace

Hi, got the same problem here. Here's a trace of the postinst script: Setting up apache (1.3.34-3) ... + . /usr/share/debconf/confmodule ++ '[' '!' '' ']' ++ PERL_DL_NONLAZY=1 ++ export PERL_DL_NONLAZY ++ '[' '' ']' ++ exec /usr/share/debconf/frontend /var/lib/dpkg/info/apache.postinst

Bug#383267: subprocess post-installation script returned error exit status 10

severity 383267 important merge 383267 358543 thanks Already known about - it's a change in behaviour in debconf, we're working on a fix. -Thom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#383267: postinst incorrectly concatenating apache/server-name with value

Package: apache Version: 1.3.34-3 Followup-For: Bug #383267 I did a set -x on /var/lib/dpkg/info/apache.postinst After doing the db_conf section, I noticed this: + db_set apache/server-name apu.exley.net + _db_cmd 'SET apache/server-name' apu.exley.net + printf '%s\n' 'SET

Processed: Re: Bug#383267: subprocess post-installation script returned error exit status 10

Processing commands for [EMAIL PROTECTED]: severity 383267 important Bug#383267: subprocess post-installation script returned error exit status 10 Severity set to `important' from `grave' merge 383267 358543 Bug#358543: apache: fails to install Bug#383267: subprocess post-installation script

Bug#358543: postinstall of apache and apache-ssl 1.3.34-3 also fail - db_* workaround may help

The same bug is in versions 1.3.34-3 of apache and apache-ssl. The workaround (quoting the db_set lines) worked for apache-ssl, but the postinstall script of apache needed another quoting of other db_* lines. For me, an strace -f of the dpkg -i command revealed the error (when looking for

Bug#383267: error processing apache (--configure)

Package: apache Version: 1.3.34-3 same bug here output is here /var/lib/dpkg/info# DEBCONF_DEBUG=developer debconf apache.postinst debconf (developer): starting apache.postinst Can't exec apache.postinst: No such file or directory at /usr/share/perl/5.8/IPC/Open3.pm line 168. open2: exec of

Bug#383285: apache: Error 10 in postinst

Package: apache Version: 1.3.34-3 Severity: important Hi ! This bug may be related to #366843. When configuring, apache fails in postinst with error 10. Here is the end of sudo /usr/share/debconf/frontend sh -xv /var/lib/dpkg/info/apache.postinst configure : + db_set apache/server-name

Problem with interrupted requests

I've realised a very annoying difference between apache 1.3.33 and 2.0.54 (using mpm-prefork): Executing the PHP script '? while(1){sleep(10);} ?' and pressing the 'Stop' button of your browser or stopping your browser itself would result into an apparently never ending process and a half open

Bug#353443: marked as done (Apache2 : SSLVerifyClient directive in location make post to PHP script impossible)

Your message dated Wed, 16 Aug 2006 14:02:31 +0200 with message-id [EMAIL PROTECTED] and subject line Fixed in NMU of apache2 2.2.3-1~exp.r170 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

Processed: Re: Fixed in NMU of apache2 2.2.3-1~exp.r170

Processing commands for [EMAIL PROTECTED]: Version: 2.2.3-1~exp.r170 Unknown command or malformed arguments to command. tag 236193 - fixed Bug#236193: apache2-mpm-perchild: graceful restart doubles number of threads Tags were: fixed Tags removed: fixed tag 238586 - fixed Bug#238586:

Bug#285337: marked as done (apache2-mpm-worker: Apache is unable to serve a file of 4Gb size)

Your message dated Wed, 16 Aug 2006 14:02:31 +0200 with message-id [EMAIL PROTECTED] and subject line Fixed in NMU of apache2 2.2.3-1~exp.r170 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#273929: marked as done (a2{en,dis}mod system needs a way to track dependencies)

Your message dated Wed, 16 Aug 2006 14:02:31 +0200 with message-id [EMAIL PROTECTED] and subject line Fixed in NMU of apache2 2.2.3-1~exp.r170 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

apache_1.3.34-4_i386.changes ACCEPTED

Accepted: apache-common_1.3.34-4_i386.deb to pool/main/a/apache/apache-common_1.3.34-4_i386.deb apache-dbg_1.3.34-4_i386.deb to pool/main/a/apache/apache-dbg_1.3.34-4_i386.deb apache-dev_1.3.34-4_all.deb to pool/main/a/apache/apache-dev_1.3.34-4_all.deb apache-doc_1.3.34-4_all.deb to

Bug#344072: Fixed in NMU of apache2 2.2.3-1~exp.r170

Version: 2.2.3-1~exp.r170 tag 236193 - fixed tag 238586 - fixed tag 241223 - fixed tag 273929 - fixed tag 285337 - fixed tag 337817 - fixed tag 340538 - fixed tag 340955 - fixed tag 341460 - fixed tag 343467 - fixed tag 344072 - fixed tag 348189 - fixed tag 353443 - fixed tag 368497 - fixed tag

Bug#368497: marked as done (grep complains about empty mods-enabled directory within apache2 init script)

Your message dated Wed, 16 Aug 2006 14:02:31 +0200 with message-id [EMAIL PROTECTED] and subject line Fixed in NMU of apache2 2.2.3-1~exp.r170 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#238586: marked as done (apache2-mpm-perchild: BusyWorkers and IdleWorkers always 0)

Your message dated Wed, 16 Aug 2006 14:02:31 +0200 with message-id [EMAIL PROTECTED] and subject line Fixed in NMU of apache2 2.2.3-1~exp.r170 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#344072: marked as done (apache2: Apache 2.2 has been released)

Your message dated Wed, 16 Aug 2006 14:02:31 +0200 with message-id [EMAIL PROTECTED] and subject line Fixed in NMU of apache2 2.2.3-1~exp.r170 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#379015: marked as done (apache2-common: Ugly error messages when /etc/apache2/conf.d/ is empty)

Your message dated Wed, 16 Aug 2006 14:02:31 +0200 with message-id [EMAIL PROTECTED] and subject line Fixed in NMU of apache2 2.2.3-1~exp.r170 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#236193: marked as done (apache2-mpm-perchild: graceful restart doubles number of threads)

Your message dated Wed, 16 Aug 2006 14:02:31 +0200 with message-id [EMAIL PROTECTED] and subject line Fixed in NMU of apache2 2.2.3-1~exp.r170 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#340538: marked as done (apache2: includes non-free and possibly undistributable files)

Your message dated Wed, 16 Aug 2006 14:02:31 +0200 with message-id [EMAIL PROTECTED] and subject line Fixed in NMU of apache2 2.2.3-1~exp.r170 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#340955: marked as done (apache2-common: default /etc/apache2/apache2.conf uses non-POSIX globs in Includes)

Your message dated Wed, 16 Aug 2006 14:02:31 +0200 with message-id [EMAIL PROTECTED] and subject line Fixed in NMU of apache2 2.2.3-1~exp.r170 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#244897: marked as done (Problems with big files (size over 2 gigabytes))

Your message dated Wed, 16 Aug 2006 14:02:31 +0200 with message-id [EMAIL PROTECTED] and subject line Fixed in NMU of apache2 2.2.3-1~exp.r170 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#241223: marked as done (apache2-common: missing largefile (2GB) support)

Your message dated Wed, 16 Aug 2006 14:02:31 +0200 with message-id [EMAIL PROTECTED] and subject line Fixed in NMU of apache2 2.2.3-1~exp.r170 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#343467: marked as done ([CVE-2005-3352] XSS issue in mod_imap)

Your message dated Wed, 16 Aug 2006 14:02:31 +0200 with message-id [EMAIL PROTECTED] and subject line Fixed in NMU of apache2 2.2.3-1~exp.r170 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#341460: marked as done (apache2: can't serve big files)

Your message dated Wed, 16 Aug 2006 14:02:31 +0200 with message-id [EMAIL PROTECTED] and subject line Fixed in NMU of apache2 2.2.3-1~exp.r170 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#358543: marked as done (apache: fails to install)

Your message dated Wed, 16 Aug 2006 05:47:08 -0700 with message-id [EMAIL PROTECTED] and subject line Bug#358543: fixed in apache 1.3.34-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#358543: marked as done (apache: fails to install)

Your message dated Wed, 16 Aug 2006 05:47:08 -0700 with message-id [EMAIL PROTECTED] and subject line Bug#383267: fixed in apache 1.3.34-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#381893: marked as done (apache: does evil things with IFS in postinst)

Your message dated Wed, 16 Aug 2006 05:47:08 -0700 with message-id [EMAIL PROTECTED] and subject line Bug#381893: fixed in apache 1.3.34-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#361217: marked as done ([INTL:gl] Galician debconf templates translation)

Your message dated Wed, 16 Aug 2006 05:47:08 -0700 with message-id [EMAIL PROTECTED] and subject line Bug#361217: fixed in apache 1.3.34-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#383267: marked as done (subprocess post-installation script returned error exit status 10)

Your message dated Wed, 16 Aug 2006 05:47:08 -0700 with message-id [EMAIL PROTECTED] and subject line Bug#383267: fixed in apache 1.3.34-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#383267: marked as done (subprocess post-installation script returned error exit status 10)

Your message dated Wed, 16 Aug 2006 05:47:08 -0700 with message-id [EMAIL PROTECTED] and subject line Bug#358543: fixed in apache 1.3.34-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#364354: marked as done (apache: [INTL:sv] Swedish debconf templates translation)

Your message dated Wed, 16 Aug 2006 05:47:08 -0700 with message-id [EMAIL PROTECTED] and subject line Bug#364354: fixed in apache 1.3.34-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

Processing of apache_1.3.34-4_i386.changes

apache_1.3.34-4_i386.changes uploaded successfully to localhost along with the files: apache_1.3.34-4.dsc apache_1.3.34-4.diff.gz apache-doc_1.3.34-4_all.deb apache-dev_1.3.34-4_all.deb apache_1.3.34-4_i386.deb apache-ssl_1.3.34-4_i386.deb apache-perl_1.3.34-4_i386.deb

Slightly extending ssl-cert package capabilities

Greetings, I am building packages for nufw [1], which require that I generate both a SSL key and certificate. This is a pain to do with openssl, and it cannot be done directly (in my understanding) by using the make-ssl-cert : that command can only (in my understanding) generate a key. Would you

Bug#366843: apache: same problem here...

Followup-For: Bug #366843 Package: apache Version: 1.3.34-3 ...but with the latest unstable package. here is some info: , | ... | + '[' '!' /var/www ']' | + '[' apache '!=' apache-ssl ']' | + '[' '!' 80 ']' | + '[' '!' localhost ']' | + db_set apache/server-name localhost | + _db_cmd 'SET

Bug#366843: apache: same problem here...

Cristian Ionescu-Idbohrn wrote: Version: 1.3.34-3 | dpkg: error processing apache (--configure): | subprocess post-installation script returned error exit status 10 This is already fixed in 1.3.34-4. ... Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe.