similar to: puppet 2.6.12 for Solaris available at OpenCSW

Just rolled, so it''s in my experimental area at the mo. I''m just about to test it, others please feel free to do so too. http://buildfarm.opencsw.org/experimental.html#markp Once I''ve confirmed it''s OK I''ll push to the main catalog. You might like to hang on for that event. --Mark -- You received this message because you are subscribed to the

Folks, OpenCSW have released Facter 1.6.0 for Solaris - this includes a back port of the patch for issue 7038[1]. It''s been released to the current catalog, but for now you can pick it up at http://buildfarm.opencsw.org/experimental/html#markp Regards, --Mark [1] http://projects.puppetlabs.com/issues/7038 -- You received this message because you are subscribed to the Google Groups

Folks, I''ve rolled 2.7.9 for Solaris as an OpenCSW package[1]. You can get it from the ''unstable'' catalog now. Regards, --Mark [1] http://www.opencsw.org/packages/puppet & http://www.opencsw.org/packages/puppetmaster -- Mark Phillips http://probably.co.uk http://vntx.cc -- You received this message because you are subscribed to the Google Groups

Puppet 3.2.4 is now available. 3.2.4 addresses two security vulnerabilties discovered in the 3.x series of Puppet. These vulnerabilities have been assigned Mitre CVE numbers CVE-2013-4956 and CVE-2013-4761. All users of Puppet 3.2.3 and earlier are strongly encouraged to upgrade to 3.2.4. For more information on these vulnerabilities, please visit http://puppetlabs.com/security/cve/cve-2013-4761

Hello Timo, from the maintainer of the OpenCSW package I got the below answer. As the newly build package yields another different commit hash (which I cannot find on GitHub too), I would ask, if you are sure that the commit hash-output in 'doveconf -n' is generated correctly? The headline of 'doveconf -n' with the newly build package is # 2.2.25 (68082dc):

Hi Jake, thanks for fixing this. I have installed now the newly built package on my production system and will report, if any more core dumps occur. Regards, Andreas Am 31.08.2016 um 20:19 schrieb Jake Goerzen: > Hi Andreas & Timo, > > > I've found out what is causing the incorrect hash in the built > packages. Our build system use here at OpenCSW has internal git

Puppet 2.6.12 is a security update release in the 2.6.x branch. The only changes since 2.6.11 are security fixes for the following vulnerability: * CVE-2011-3872, Altnames Vulnerability For more details on this vulnerability, follow the link on our blog post: http://puppetlabs.com/blog/important-security-announcement-altnames-vulnerability/ Other information available at:

Puppet 3.0.0-rc5 is a feature release candidate for the 3.x series of Puppet. Downloads are available at: * Source http://downloads.puppetlabs.com/puppet/puppet-3.0.0rc5.tar.gz RPMs are available at http://yum.puppetlabs.com Debs are available at http://apt.puppetlabs.com Gems are available via rubygems at https://rubygems.org/downloads/puppet-3.0.0.rc5.gem or by using `gem install --pre

----- Forwarded message from Nick Lewis <nick@puppetlabs.com> ----- Date: Thu, 3 Feb 2011 21:59:10 -0800 From: Nick Lewis <nick@puppetlabs.com> To: puppet-users@googlegroups.com, puppet-dev@googlegroups.com Subject: [Puppet-dev] ANNOUNCE: Puppet 2.6.5 - Release Candidate 1 available! Message-ID: <AANLkTikjFwZ98P_NcxF54zHbU2mJf15XDrLg2cMp2GWT@mail.gmail.com> We''re back

We''re back with a maintenance release: 2.6.5. This release addresses a number of bugs in the 2.6.x branch. 2.6.5 is a maintenance release in the 2.6.x branch and it contains only bug fixes, documentation updates and a small handful of features. The first release candidate is available for download at: http://puppetlabs.com/downloads/puppet/puppet-2.6.5-rc1.tar.gz We''re

Hi Folks, Our Mac clients are running Puppet 2.7.6 (via Mac Ports) but get the following error when trying to connect to our 2.6.9 server: > err: Could not retrieve catalog from remote server: Error 400 on SERVER: No support for http method POST > info: Not using expired catalog for client.example.com from cache; expired at Wed Feb 22 23:30:29 -0800 2012 > notice: Using cached catalog

I have two different server type. Once is debian 6.0 squeeze and puppet version is "2.6.2". And other Ubuntu 12.04 and puppet version 2.7.11. Puppet master server is Ubuntu 12.04. I write something in /etc/crond.d/puppetcron which works specific time. Problem is if debian servers have any changes, don''t send mail me but ubuntu server send mail when every work like this:

Hi, I''ve got a problem where clients apparently randomly lose the ability to retrieve catalogs. This is what I end up seeing in the log: puppet-agent[26510]: Starting Puppet client version 2.6.6 puppet-agent[26510]: Could not retrieve catalog from remote server: puppet-agent[26510]: Using cached catalog puppet-agent[26510]: Could not retrieve catalog; skipping run Notice that no

I''m not really sure the problem is a Plugin problem!! Note than a puppet client was installed, i change the setting of ip/hosname and try to re inscription the node to puppetmaster. I would like to understand what happen. The errors/warnings messages are not very easy to understand and sometime i''m lost. thank you for you advice. Eric Puppet version: 0.25.4-2ubuntu6

I''ve been hitting this issue for a long time. well over a year and I guess it''s time to start pushing it to try to find the root cause. I''ve seen this reported several times in the past but I''ve never seen a resolution found for this exact problems. There are other root causes for pson errors that have been resolved, but not for the ones describing my

Today I was testing Puppet''s fileserver feature and and error came up: client> /usr/sbin/puppetd --test --verbose --server puppet info: Caching catalog at /var/lib/puppet/localconfig.yaml notice: Starting catalog run notice: //Node[default]/sudo/Package[sudo]/ensure: created err: //Node[default]/sudo/File[/etc/sudoers]: Failed to retrieve current state of resource: No specified source

I have followed many tutorials including the ones provided by puppetlabs and I keep seeing the same issues. I began by installing puppet on machine: puppet001, and puppet master on machine: puppetMaster. The hosts files were then configured so that both machines were reachable by the machine name. The puppet.conf files were then updated, and a cert was generated and sent from puppet001 to

Hello, I was trying to change two modules on my puppet. And I was block on one error, until I figured that the error which show up was not related to a specific module. This error is causing issue to all my puppet clients : #puppetd -vt info: Retrieving plugin err: Could not retrieve catalog from remote server: Error 400 on SERVER: compile error (erb):416: syntax error, unexpected kEND,

Puppet 2.7.18 is a security release in the 2.7.x branch. The security changes in 2.7.18 address CVEs 2012-3864, 2012-3865, 2012-3866 and 2012-3867. All users of Puppet 2.7.x are encouraged to upgrade when possible to Puppet 2.7.18. More information available at http://puppetlabs.com/security or visit http://puppetlabs.com/security/cve/cve-2012-3864,

> Adam, you should be able to either grab the unstable deb from here: > > http://packages.debian.org/sid/puppet > > or build from source using git-buildpackage, this post describes how: > > http://explanatorygap.net/2009/10/29/puppet-0-25-1-debs-done-but-dela... Thank you very much!! I have already tried the debian-experimental packages on both Ubuntus, but I finally gave up