On 2/23/2009 7:15 AM, Ohad Levy wrote: > Your only way around this is to install the package before the first > puppet run or wait for the second run (and handle the nil value in > the template...)
The first option is what I've always done. Since I'm spending part of the morning rebuilding a system with a new hard drive in it, I'm also working up putting newer Puppet and Facter packages into my Debian etch preseed installs with: # Add openssh-server plus newer puppet dependencies d-i pkgsel/include string openssh-server ruby libxmlrpc-ruby libopenssl-ruby adduser lsb-base lsb-release libshadow-ruby1.8 d-i preseed/late_command string wget -O /target/root/facter_1.5.1-0.1_all.deb http://HOST/PATH/TO/facter_1.5.1-0.1_all.deb ; wget -O /target/root/puppet_0.24.6-1_all.deb http://HOST/PATH/TO/puppet_0.24.6-1_all.deb ; in-target dpkg --force-confold -i /root/facter_1.5.1-0.1_all.deb /root/puppet_0.24.6-1_all.deb ; wget -O /target/etc/puppet/puppet.conf http://HOST/PATH/TO/puppet.conf For existing installations, I'd just replace 'ssh host "apt-get install puppet"' with 'ssh host "apt-get install lsb-release puppet"' -- Mike Renfro / R&D Engineer, Center for Manufacturing Research, 931 372-3601 / Tennessee Technological University --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
