The standard provider doesn't work with packages that have multiple origins (the apache ports for instance) because the package name doesn't match was is recorded in the package database. So, what will happen is that puppet will think the package isn't installed on every run and attempt to install it.
The only sane way around that was to use the package origin as a key and duplicated the '-r' functionality in the provider; this is what the patch does. Passing '-f' to pkg_add was questionable, but I remember there being problems without it. On Thursday, August 8, 2013 6:09:07 AM UTC-7, badgerious wrote: > > Did you install puppet from ports? I did a 3.2.3 install recently and > noticed that there is a > patch<http://svnweb.freebsd.org/ports/head/sysutils/puppet/files/optpatch-package_origin?revision=311088&view=markup>in > that port that reverts back to an older version of the freebsd package > provider, apparently for ruby 1.8 compatibility. I got rid of the > optpatch-package_origin file and reinstalled the port to get the proper > package provider, which does indeed use '-r'. > > Eric > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
