[Puppet Users] Re: Freebsd + Puppet 3.2.2 pkg_add -f ?

2013-12-09 Thread Pawel Tomulik
Hi, you may try this module: http://forge.puppetlabs.com/ptomulik/packagex which implements `portsx` provider (FreeBSD ports). W dniu środa, 7 sierpnia 2013 17:17:33 UTC+2 użytkownik joel johnston napisał: Shouldn't pkg_add be using the -r option for package management? I worked around by

Re: [Puppet Users] Re: Freebsd + Puppet 3.2.2 pkg_add -f ?

2013-08-26 Thread Russell Jackson
I've had a little time to look at this. What looks to be happening is that the URI class adds a hard leading slash to ftp:// uri path components which fetch(1) doesn't handle well. You can work around this by setting the package resource's 'source' parameter to use the http:// scheme. Set it

Re: [Puppet Users] Re: Freebsd + Puppet 3.2.2 pkg_add -f ?

2013-08-24 Thread joel johnston
The real isssue I seem to be having is that puppet agent is ignoring my PACKAGESITE variable. I've set it accordingly per: http://projects.puppetlabs.com/projects/puppet/wiki/Puppet_Free_Bsd/8 pkg_add -r whatever works fine from the command line in bash and sh, but puppet runs use the url above

Re: [Puppet Users] Re: Freebsd + Puppet 3.2.2 pkg_add -f ?

2013-08-21 Thread Eugene Vilensky
On Tue, Aug 20, 2013 at 2:15 PM, joel johnston joeldjohns...@gmail.com wrote: The url is bad/wrong. For some reason it is injecting this %2F in front of pub where it SHOULD just be /pub/ %2F is a '/' in url encoding, maybe there is a trailing slash somewhere you can remove which will allow

Re: [Puppet Users] Re: Freebsd + Puppet 3.2.2 pkg_add -f ?

2013-08-20 Thread joel johnston
So I think the core issue at this point is that no matter where I try to set PACKAGESITE (on the server via rc, on the client via rc, on the shell via overrides) the path to the ftp server always returns: Error: /Stage[main]/Rsync/Package[net/rsync]/ensure: change from absent to present failed:

[Puppet Users] Re: Freebsd + Puppet 3.2.2 pkg_add -f ?

2013-08-12 Thread Russell Jackson
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

[Puppet Users] Re: Freebsd + Puppet 3.2.2 pkg_add -f ?

2013-08-12 Thread badgerious
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

[Puppet Users] Re: Freebsd + Puppet 3.2.2 pkg_add -f ?

2013-08-08 Thread badgerious
Did you install puppet from ports? I did a 3.2.3 install recently and noticed that there is a patchhttp://svnweb.freebsd.org/ports/head/sysutils/puppet/files/optpatch-package_origin?revision=311088view=markupin that port that reverts back to an older version of the freebsd package provider,