Package provider that depends on another package (PEAR)
Ben Beuchler
http://www.mit.edu/~marthag/puppet/pear.rb
It works quite well, but on a freshly installed system package
prefetching fails if the "pear" tool is not yet installed. Is there
some way to disable the prefetch if PEAR doesn't exist, only
attempting to use the PEAR provider once its prerequisites have been
installed?
Currently all PEAR packages fail to install on the first pass,
requiring a second run of puppetd to install them.
Thanks!
-Ben
root@test02:~# puppetd --test
info: Retrieving plugins
notice: Ignoring cache
info: Caching catalog at /var/lib/puppet/state/localconfig.yaml
notice: Starting catalog run
err: Could not prefetch package provider 'pear': Could not list pears:
Execution of ' list' returned 256:
[:snip:]
Peter Meier
> I've installed this PEAR package provider:
> http://www.mit.edu/~marthag/puppet/pear.rb
>
> It works quite well, but on a freshly installed system package
> prefetching fails if the "pear" tool is not yet installed. Is there
> some way to disable the prefetch if PEAR doesn't exist, only
> attempting to use the PEAR provider once its prerequisites have been
> installed?
>
> Currently all PEAR packages fail to install on the first pass,
> requiring a second run of puppetd to install them.
which version are your running? Because I think I had a similar problem
with another custom type: http://markmail.org/message/mztfu6hw47qmbleq
and It seems to be fixed. well at least I didn't encounter the problem
anymore after 0.24.4
cheers pete
Ben Beuchler
From reading your thread it sounds like we have similar, but not quite
identical, problems. In my case it's because the custom type is a
provider for the "package" type. As a result it tries to prefetch the
status of its packages, which fails.
-Ben