[Pkg-puppet-devel] puppetlabs-firewall and puppetlabs-postgresql ready for review/upload
Stig Sandbeck Mathisen
ssm at debian.org
Fri Sep 27 19:14:30 UTC 2013
Thomas Bechtold <thomasbechtold at jpberlin.de> writes:
> Hi Stig,
>
> I packaged puppetlabs-firewall[1] and puppetlabs-postgresql[2]. Please
> have a look and upload them if you are happy with the packages.
>
> One comment for the postgres-package: I changed one dependency from
> ripienaar-concat to puppetlabs-concat. This results in a warning when
> you execute "puppet module list". The dependency is already fixed in
> upstream git so the next upstream release will eliminate the warning.
I think the puppet packages do not need to depend on the os packages
they may install where applied.
puppet-module-puppetlabs-firewall
---------------------------------
The package depends on iptables and ebtables. The admin may not have, or
even want, those installed on their puppet master.
When included in a manifest and compiled to a catalog, the "firewall"
puppet class will install "iptables" on systems where this class is
applied.
A "Suggests:" for these two dependencies should be sufficient to add a
hint to the admin that the two packages are related to
puppet-module-puppetlabs-firewall.
puppet-module-puppetlabs-postgresql
-----------------------------------
Same as for the previous package, the "postgresql-client-common"
dependency should not be installed on the puppet master, as it is not
needed when compiling a manifest to a catalog, but a "Suggests:" will
add a hint.
--
Stig Sandbeck Mathisen
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-puppet-devel/attachments/20130927/9be00652/attachment.sig>
More information about the Pkg-puppet-devel
mailing list