Bug#220041: modules-update has a will of its own.
On Tue, 11 Nov 2003, David Röhr wrote:
> 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.
No problem at all, don't worry. There is still a point open in both your
and the other bug but it's "less" important, that's why i downgraded it to
normal and merged with the other one (just read below).
> > 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.
Well yes. This is mandate for modules that are in /usr/lib/apache/1.3.
It's the only way we have to perform certain operations since it is almost
impossible to gather them from the module itself.
> > 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.
Well that would have happen in any other system as well :-)
> > 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.
I was checking Debian Policy in this regard but i couldn't find anything
specific other than few words but i will have to dig this a bit more
before giving an appropriate answer.
> > 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.
modules.conf is recreated each upgrade and it is based on the old one BUT
only if the information provided are correlated to the info file that is
used later on to rebuild the correct LoadModule sequence. It's not that
simple as it looks like.
> 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?"
This was the other issue related to the other bug that's why they are not
closed yet.
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: