Bug#220041: modules-update has a will of its own.

[David Röhr <david@rohr.se>]

So when upgrading and using external modules that doesn't follow with
debian, the module.conf will break every time?

There must be alot of users that use modules doesn't follow with Debian,
commercial modules. And it works great adding them. And using
modules.conf, but on every upgrade the modules.conf removes them. Should
not modules.conf (if existed) be based on the last one?

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.

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. Same if you wish to update modules.conf or httpd.conf.

Something like the sendmail package. Wich ask if you want to change any
configuration, and if you want to start the server efter the upgrade.


/d

-- 
... david röhr              |      o_
.. unix systems consultant  | o/  /\   Solaris, AIX, HP-UX
. qbranch system management | /|_, \\   and GNU/Linux Certified.
        www.qbranch.se        /                    
                              `