Bug#220041: modules-update has a will of its own.
On Tue, 11 Nov 2003 [07:08],
Fabio Massimo Di Nitto (fabbione@fabbione.net) wrote:
> 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.
Ah, He seems to have the same problem that I do, I'm sorry to say that I
missed that bug report before reporting.
> 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
So my module breaks of the lack of info-files? If so, I see no problem
fixing it, since the info-files are fairly easy to make.
> 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.
Ah. I just had to add the connection between the failure of loading some
directive in httpd.conf (beacause modules.conf fails) then makes apache
not installable.
> 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.
When installing/upgrading the service ask if you want to restart your
ssh. Even if this breaks you still have an active ssh-session that isn't
closed just because the server restarts or stops.
This is just because if something goes wrong on the upgrade, like an
configuration error, you shouldn't be locked out. And then you could
easy downgrade or fix the problem.
> 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.
I have read this. But I didn't think that the modules.conf would be recreated
in every upgrade, and not be based on the last modules.conf. But now it
seems that it removes mod_throttle just because the lack of an info
file. Should that give some error? Like "Removing mod_throttle, no
info-files found" or something. Or even better, "Can't find any
info-files with mod_throttle, using it may cause your system to be
unusable, continue?"
/d
--
... david röhr | o_
.. unix systems consultant | o/ /\ Solaris, AIX, HP-UX
. qbranch system management | /|_, \\ and GNU/Linux Certified.
www.qbranch.se /
`
Reply to: