search for: providerapt

...; Package <| |> and in the run itself I see debug: /Stage[main]/Apt/Exec[apt-update]/before: requires Package[libmysqlclient-dev] debug: /Stage[main]/Apt/Exec[apt-update]/before: requires Package[mysql-server] but then it does the following without the update debug: Puppet::Type::Package::ProviderApt: Executing ''/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold --force-yes install libmysqlclient-dev=5.1.*'' Not sure if this correct but it definitely doesn''t appear to be doing the update Any help most appreciated, Will -- You received this message becaus...

.../sbin/nimclient does not exist debug: Puppet::Type::Package::ProviderZypper: file /usr/bin/zypper does not exist debug: Puppet::Type::Package::ProviderSunfreeware: file pkg-get does not exist debug: Puppet::Type::Package::ProviderOpenbsd: file pkg_delete does not exist debug: Puppet::Type::Package::ProviderApt: file /usr/bin/apt-get does not exist [...] why does puppet check what service/package type provider has to use if it''s defined? 2.- ) file-metadata I have ~hundred messages like: debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw yaml; using pson is it a line for ea...

...Puppet::Type::Package::ProviderRpm: Executing ''/bin/rpm --version'' debug: Puppet::Type::Package::ProviderYum: Executing ''/bin/rpm --version'' debug: Puppet::Type::Package::ProviderUrpmi: Executing ''/bin/rpm -ql rpm'' debug: Puppet::Type::Package::ProviderAptrpm: Executing ''/bin/rpm -ql rpm'' debug: Puppet::Type::Package::ProviderHpux: file /usr/sbin/swinstall does not exist debug: Puppet::Type::Package::ProviderAppdmg: file /Library/Receipts does not exist debug: Puppet::Type::Package::ProviderFink: file /sw/bin/fink does not exist deb...

...e /usr/bin/rug does not exist debug: Puppet::Type::Package::ProviderOpenbsd: file pkg_delete does not exist debug: Puppet::Type::Package::ProviderSunfreeware: file pkg-get does not exist debug: Puppet::Type::Package::ProviderPortage: file /usr/bin/emerge does not exist debug: Puppet::Type::Package::ProviderAptitude: file /usr/bin/aptitude does not exist debug: Puppet::Type::Package::ProviderRpm: file rpm does not exist debug: Puppet::Type::Package::ProviderYum: file rpm does not exist debug: Puppet::Type::Package::ProviderPkg: file /usr/bin/pkg does not exist debug: Puppet::Type::Package::ProviderGem: fi...

my base/default includes this ntp manifest # cat modules/ntp/manifests/ntp.pp # ntp.pp class ntp { case $operatingsystem { centos, redhat: { $service_name = ''ntpd'' $conf_file = ''ntp.conf.el'' } debian, ubuntu: { $service_name = ''ntp'' $conf_file = ''ntp.conf.debian'' } } package {

...l pson raw yaml; using pson debug: Using cached certificate for ca debug: Using cached certificate for node12.localdomain debug: Using cached certificate_revocation_list for ca debug: Puppet::Type::Package::ProviderRpm: Executing ''/bin/rpm -- version'' debug: Puppet::Type::Package::ProviderAptrpm: Executing ''/bin/rpm -ql rpm'' debug: Puppet::Type::Package::ProviderUrpmi: Executing ''/bin/rpm -ql rpm'' debug: Puppet::Type::Package::ProviderYum: Executing ''/bin/rpm -- version'' /usr/lib/ruby/site_ruby/1.8/puppet/provider/package/msi.rb:50:...

Hello, Why the following lines doesn''t work? cron { "app" : command => ""nice -n -10 /usr/bin/php /var/www/public_html/rotinas/rotinas.php 2>&1>> /var/log/app.log", environment => "PATH=$PATH", user => root, hour => ''*'', minute =>

I too have been pushed into Puppet 3.0. Clients and PuppetMaster are now at 3.0.0. Not sure if this is a version change or syntax error that I am experiencing. We''ll use ''ntp'' as the example and the "build" host is a VM. The old way: class baseline::ntpd { package { "ntp": ensure => $virtual ? { physical => present,

Hello, we have one puppet server managing approx servers, all FreeBSD. The problem is that the puppet clients all hangs, one by one, eventually. They will run for anything between an hour up to a week. But eventually the all hang. We really like puppet and want to keep using it. But the way it is now is completely unusable. We''ve tried many versions, from 24.x, and now 2.6.1rc1. But