[Puppet Users] Re: EPEL package dependencies

Todd Zullinger
2009-05-27T15:24:21Z

Rob McBroom wrote:
> This may or may not be the right place to ask this, but I''m sure
> it''ll lead me there.
>
> I''m using Puppet packages from EPEL (thanks to whoever provides
> these).

Heh, the hard work is writing puppet.  Packaging it is relatively
simple.

> I pushed out some new configs that use Augeas to make changes and
> they threw errors on most of my servers. Installing the "augeas"
> package made puppetd happy. (ruby-augeas and augeas-libs had already
> been pulled in when I installed puppet.)

What did the manifests look like?  What were the errors?  And what
versions of puppet, augeas, and ruby-augeas? :)

I have epel-testing enabled and these versions:

augeas-libs-0.5.0-2.el5
puppet-0.25.0-0.1.beta1.el5
ruby-augeas-0.2.0-1.el5

A simple config like this works fine without augeas installed:

    augeas { ''poppassd'':
        context => ''/files/etc/xinetd.d/poppassd/poppassd'',
        changes => [
            ''set /disable no'',
            ''set /bind 127.0.0.1'',
        ],
        require => Package[''poppassd''],
        notify  => Service[''xinetd''],
    }

> I was thinking the puppet package should list the augeas package as a
> dependency, but perhaps the ruby-augeas package can''t function
without
> it in any context, in which case the dependency should be there. If
> anyone knows, I''ll try to contact the appropriate package
maintainer
> to let them know (assuming they aren''t already reading this).

Most of us probably are.  At least, enough of us to help figure out if
there is a packaging bug and who to point the finger at for a fix. ;)

--
Todd        OpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
How much does it cost to entice a dope-smoking UNIX system guru to
Dayton?
    -- Brian Boyle, UNIX/WORLD''s First Annual Salary Survey