Bug#220041: modules-update has a will of its own.
On Mon, 10 Nov 2003, David Röhr wrote:
> So when upgrading and using external modules that doesn't follow with
> debian, the module.conf will break every time?
This depends on where and how you install external module that are not
part of Debian. Please look at this bug report.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=214773
where we discussed the same issues.
As well you might be interested in checking this document that will be
part of apache_1.3.29-2
http://cvs.raw.no/cgi-bin/viewcvs.cgi/*checkout*/debian-apache/debian/README.modules?content-type=text%2Fplain&rev=1.5
> Another bug is (when the configuration break), and the apache server
> can't started due to an configuration failure, the upgrade should still
> work, and it should not break just for an httpd.conf-error.
Please do not report more than one issue at a time in the same bug report.
It makes very difficult for us to handle them. The Debian bug tracking
system doesn't permit us to split a bug into several.
In any case such a feature is simply impossible to have since if for
example a module is not there anymore (like it happened for you and
mod_throttle) there is no way for us to keep apache working.
> After an upgrade, the server should not be started automaticly at all,
> or there should be a question of wich you want to start the server or
> not.
This would break other users expectations. Imagine doing this to ssh.. you
shut the service down, during the upgrade something goes wrong and you
cannot login in anymore.
> Same if you wish to update modules.conf or httpd.conf.
We changed policy for this as well in 1.3.28. The debconf message from
apache-common should have notified you. modules.conf is not a file that
users should edit and it was the last change that we perform. From now on
only modules.conf will be handled by debian and critical changes to the
configuration that would make apache unuseable 100%. All the other small
details are "suggested changes" and reported in
/etc/apache/suggested_correction.
Fabio
--
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues
http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp00004.html
Reply to: