search for: dreese

...e them: package { "packagename": ensure => latest, schedule => "daily", tag => "manualrun" } the package installation doesn''t get done if I call "puppetd --tag manualrun" because the schedule is not satisfied. Any ideas? Thanks, Jeremy Dreese

I have found a few issues with puppet and the up2date provider (version 0.22.4) that I''d like to run by those who use up2date (to see if others are experiencing the same issues). 1. Puppet doesn''t seem to find the latest updates of packages that are already installed. In looking at "/usr/lib/site_ruby/1.8/puppet/provider/package/up2date.rb", I found that

I have been looking at Puppet as a possible replacement for cfengine at our site. One difficulty I''ve had with cfengine that I''m wondering if Puppet can solve is that of dealing with laptop/mobile users. Since these laptops move around quite a bit, their IP/hostname is constantly changing. From playing with puppet a bit, I''ve found that it seems to generate the

Hi Luc, do you know if Ticket #743 will be solved in the next release ? it''s a trivial change of command line option in the provider from --show-available to --showall, --show-available does not list installed packages so you cannot upgrade a package ( if allready installed and a new version comes the provider will not see it rendering the ensure=> latest useless). It could be