Age | Commit message (Collapse) | Author |
|
|
|
installed on Debian systems that are not lenny (would be nice if we could use operators for lsbdistcode name like 'if $lsbdistcodename >> "lenny")
on Debian Squeeze and later, the munin-node package requires that munin-common be installed. this would normally be handled automatically by the packaging system, but if you utilize the $munin_node_ensure_version variable to set it to the backports version, and you have backports pinned properly (as the shared-apt module does it), it will fail to install the munin-common package from backports.
you would think that this change should go in the debian.pp, but that is not possible because debian.pp inherits client/package.pp and thus the order happens wrong
|
|
|
|
|
|
|
|
|
|
|
|
setup a special munin::plugins::centos and include that in the proper
client case statement for centos
|
|
|
|
|
|
not see what the bug is, and this interferes with local installation of the plugin (causes duplicate definitions)"
It looks like the reason this is here is because on a default debian
install, without postfix installed, this postfix munin module is
activated, leading to empty graphs. So rather that leave non-postfix
people in this situation, we can instead leave this in and the class
can be overridden locally.
This reverts commit ebfde169e0ef4fc749cd6804e707103fab7dbf78.
Conflicts:
manifests/client/debian.pp
|
|
module, we risk duplicate definitions. this commit fixes that by doing
a check to see if it is already defined elsewhere, and if it is not,
then it installs the package
|
|
|
|
what the bug is, and this interferes with local installation of the plugin (causes duplicate definitions)
|
|
|
|
|
|
|
|
|
|
|