|| at Aug 13, 2013 at 12:54 am
I should disclaim that I'm not a huge FreeBSD guy, but do have a couple of
FreeBSD boxes around. I've been content getting all packages with 'pkg_add
-r' (which seems to work fine with the unpatched freebsd provider); no idea
about the interactions with ports you've mentioned.
Couple of others things regarding the patch (semi tangential):
1) If you do an install of puppet 3.2.3 from ports with ruby 1.9.3, you get
piles of warnings during puppet runs due to some class variable use in the
freebsd provider. This is fixed in vanilla puppet 3.2.3, but undone by the
2) If the freebsd provider is broken, seems like it should be going back
upstream rather than patching in the port (forgive my ignorance if this is
in fact happening and the patch is interim).
On Monday, August 12, 2013 3:35:41 PM UTC-5, Russell Jackson wrote:
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
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.
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 email@example.com.
To post to this group, send email to firstname.lastname@example.org.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.