Your message dated Wed, 24 Jan 2007 21:36:24 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Can't reproduce, closing
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 ---
Package: torrus-apache2
Version: 1.0.4-1
Severity: serious
Usertags: grid5000 piuparts
Hi,
During a piuparts run over all the packages in etch, I ran into a
problem with your package:
Setting up torrus-common (1.0.4-1) ...
Not starting Torrus collector daemons as no configured trees found.
Not starting Torrus monitor daemons as no configured trees found.
Setting up torrus-apache2 (1.0.4-1) ...
dpkg: error processing torrus-apache2 (--configure):
subprocess post-installation script returned error exit status 4
Errors were encountered while processing:
torrus-apache2
E: Sub-process /usr/bin/dpkg returned an error code (1)
This is caused by the fact that "apache2ctl configtest" fails (bug #398535).
--
| Lucas Nussbaum
| [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ |
| jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F |
--- End Message ---
--- Begin Message ---
Hi,
torrus-apache2 dependencies guarantee that at least one working
apache2 server will be configured and started. Current apache2.2-common
package provides an initialization script /etc/init.d/apache2, which
creates an empty http.conf file, if one does not exist:
[...]
case $1 in
start)
[ -f /etc/apache2/httpd.conf ] || touch /etc/apache2/httpd.conf
[ -d /var/run/apache2 ] || mkdir -p /var/run/apache2
[...]
I have tried reproducing the bug, but when installing either
torrus-apache2 or apache2-mpm-worker, the apache2 server was properly
configured and started using that script, creating an empty
/etc/apache2/httpd.conf in the process. The torrus-apache2
configuration succeeded after that too. As I don't see any evidence of
a problem with torrus-apache2, I'm closing the bug. If you still think
something is wrong with it, feel free to reopen with more information
on how to reproduce it (in particular, part of the installation log
describing the configuration and starting of apache2 server), and I'd
be glad to look into it.
Thanks for the report,
--
Jurij Smakov [EMAIL PROTECTED]
Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC
--- End Message ---
