Re: [Puppet Users] Re: question about package provider on Solaris

2010-07-16 Thread James Turnbull
Gary Law wrote: > You could argue none of this is a problem with puppet per se, however, > I think puppet needs to move it's Solaris Blastwave provider backend > to pkgutil. > I've added a ticket for the pkgutil provider: http://projects.puppetlabs.com/issues/4258 Regards James Turnbull -- P

Re: [Puppet Users] Re: question about package provider on Solaris

2010-07-16 Thread Gary Law
> Looking at the provider, I believe blastwave provider is running the > command: pkg-get upgrade {package_name}. Please run with --debug, it should > indicate the OS command puppet to ensure latest. Try the command displayed > in debug output manually and see if it's correct and whether it perform

Re: [Puppet Users] Re: question about package provider on Solaris

2010-07-16 Thread Gary Law
On 16 July 2010 06:44, tehcook wrote: > > /opt/csw/bin/pkg-get -f upgrade common [ snip ] > [... skipped many more dependencies...] > > Current administration requires that a unique instance of the > package be created.  However, the maximum number of > instances of the package which may be supp

[Puppet Users] Re: question about package provider on Solaris

2010-07-15 Thread tehcook
Yes it runs "/opt/csw/bin/pkg-get -f upgrade common" First it was complaining about gpg missing, which I disabled in the pkg-get.conf Now it says : /opt/csw/bin/pkg-get -f upgrade common Pre-existing local file common-1.8.0,REV=2010.05.01-SunOS5.8-sparc- CSW.pkg.gz matches checksum Keeping existin

Re: [Puppet Users] Re: question about package provider on Solaris

2010-07-14 Thread Nan Liu
On Wed, Jul 14, 2010 at 12:47 PM, tehcook wrote: > I'm having similar issues with Blastwave. It does not complain about > anything and even says that package was updated. Still after the > puppet run package is at the old rev. > > puppetd -otv > Looking at the provider, I believe blastwave provi

[Puppet Users] Re: question about package provider on Solaris

2010-07-14 Thread tehcook
I'm having similar issues with Blastwave. It does not complain about anything and even says that package was updated. Still after the puppet run package is at the old rev. package { "puppet": ensure => latest, provider => "blastwave", require => P