Your message dated Thu, 19 Oct 2006 09:24:09 +0200 with message-id <45372819.6040900@err.no> and subject line Bug#393910: (no subject) 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 responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database)
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: apache2.2-common_2.2.3-1 postinst error
- From: sacrificial-spam-address@horizon.com
- Date: 2 Oct 2006 22:19:36 -0400
- Message-id: <[🔎] 20061003021936.2343.qmail@science.horizon.com>
Package: apache2.2-common Version: 2.2.3-1 This is AMD64, if it matters. I got some annoying errors trying to remove apache2-common: Removing apache2-common ... Stopping apache 2.0 web server...grep: /etc/apache2/conf.d/[^.#]*: No such file or directory apache2: Syntax error on line 116 of /etc/apache2/apache2.conf: Syntax error on line 1 of /etc/apache2/mods-enabled/cgid.load: Cannot load /usr/lib/apache2/modules/mod_cgid.so into server: /usr/lib/apache2/modules/mod_cgid.so: undefined symbol: apr_filename_of_pathname failed! invoke-rc.d: initscript apache2, action "stop" failed. dpkg: error processing apache2-common (--purge): subprocess pre-removal script returned error exit status 1 Errors were encountered while processing: apache2-common but I worked around that easily enough. The hassle came when trying to install apache2.2-common... Setting up apache2.2-common (2.2.3-1) ... touch: cannot touch `/var/log/apache2/error.log': No such file or directory touch: cannot touch `/var/log/apache2/access.log': No such file or directory dpkg: error processing apache2.2-common (--configure): subprocess post-installation script returned error exit status 1 Looking, I can's see where or how /var/log/apache2 is created, so I guess the error is obvious enough. The fix, creating the directory, requires a bit of RTFMing to figure out the required permissions. Creating the directory allows everything to go ahead. (Er... except that /usr/sbin/apache2 isn't executable... another bug report, it seems.)
--- End Message ---
--- Begin Message ---
- To: Michael Schmitz <schmitz@mail.biophys.uni-duesseldorf.de>, 393910-done@bugs.debian.org
- Subject: Re: Bug#393910: (no subject)
- From: Tollef Fog Heen <tfheen@err.no>
- Date: Thu, 19 Oct 2006 09:24:09 +0200
- Message-id: <45372819.6040900@err.no>
- In-reply-to: <[🔎] Pine.LNX.4.58.0610181401530.16064@xplor.biophys.uni-duesseldorf.de>
- References: <[🔎] Pine.LNX.4.58.0610181401530.16064@xplor.biophys.uni-duesseldorf.de>
Version: 2.2.3-2 Michael Schmitz skrev:Setting up apache2.2-common (2.2.3-1) ... touch: cannot touch `/var/log/apache2/error.log': No such file or directory touch: cannot touch `/var/log/apache2/access.log': No such file or directory dpkg: error processing apache2.2-common (--configure):This has been fixed long time ago in 2.2.3-2. - tfheen
--- End Message ---