On Thu, Jul 02, 2009 at 10:18:51AM +0200, Holger Levsen <hol...@layer-acht.org> wrote:
> it's trying to _activate_ all available plugins That seems more than a bit excessive. > You should get over it. Well, thanks for the condescension, but is it really necessary? > There is no bug. munin-node and munin-plugins-extra > consist of 104 plugins, do you propose 100 (or 30) packages for that? No. But given your response, it appears that there should be an optional package called munin-plugins which requires python. As for munin-plugins-extra, it's a package that I haven't mentioned at all (it wasn't part of the bug report, and it isn't installed according to the installation capture I provided), and it isn't relevant for this discussion. > This is as it should be. The warning should be there. It's a warning that claims that it's an error, and it provides no reasonable explanation. There is no choice for activating plugins or not in the install process, even when debconf's question priority is at its lowest. If it's not an error, it should not appear as an error, it should IMHO fail silently. There certainly should be no need to activate all available plugins without asking. Warning about things that don't need warning about, and which you cannot do anything about, is bad form. Bad form is also a bug. -- Best regards, Jan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
