similar to: Fwd: [Puppet-dev] ANNOUNCE: Puppet 2.6.5 - Release Candidate 1 available!

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

We''re back with a maintenance release: 2.6.5. This release addresses a number of bugs in the 2.6.x branch and adds a handful of features and documentation updates. This release candidate contains fixes for bugs identified in the previous release candidates: - rc1 caused a warning on Ruby 1.8.6 which could cause log pollution. This release candidate no longer generates the warning. - rc1

Hi everyone, I am in the process of evaluating Puppet (version 0.23.0 - Solaris 10 sparc), so I am still a newbie. First tests with Puppet were fine since it was running with the default configuration. Now, I have created a "puppet.conf" file ( puppetmasterd --genconfig > puppet.conf ) to customize some of the configuration parameters. When "puppet.conf" is present,

This release addresses issues with the Puppet 2.7.0rc3 series. This release is available for download at: <http://goog_1305397870/> http://www.puppetlabs.com/downloads/puppet/puppet-2.7.0rc4.tar.gz See the Verifying Puppet Download section at: http://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet Please report feedback via the Puppet Labs Redmine site, using an affected

Hey Guys, So i have puppetmaster running and well. I have a few questions 1) Even though i followed instructions on http://projects.puppetlabs.com/projects/1/wiki/Using_Mongrel on using Mongrel, puppetmaster is probably still using webrick since the client connection timeout still occurs. How do i make it use mongrel? 2) Now after messing a little with /etc/sysconfig/puppetmaster i increased

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

Puppet 3.0.1 is a bugfix release for the 3.x series of Puppet. To see a list of the issues addressed by this release, check out the 3.0.1 version in our issue tracter at: https://projects.puppetlabs.com/versions/328. This release contains contributions from the following people: Andrew Parker, Jeff McCune, Josh Cooper, Matthaus Owens, Moses Mendoza, Nick Fagerlund, Niels Abspoel, Patrick

Puppet 2.7.15rc1 is a maintenance release candidate for Puppet in the 2.7.x series. Downloads are available at: * Source http://downloads.puppetlabs.com/puppet/puppet-2.7.15rc1.tar.gz RPMs are available at http://yum.puppetlabs.com/el or /fedora Debs are available at http://apt.puppetlabs.com Mac packages are available at http://downloads.puppetlabs.com/mac/puppet-2.7.15rc1.dmg See the

Puppet 3.0.1-rc1 is a bugfix release candidate for the 3.x series of Puppet. To see a list of the issues addressed by this release, check out the 3.0.1 version in our issue tracter at: https://projects.puppetlabs.com/versions/328 Downloads are available at: * Source http://downloads.puppetlabs.com/puppet/puppet-3.0.1-rc1.tar.gz RPMs are available at http://yum.puppetlabs.com Debs are available

First of all, in the thread ''Using multiple values for source, for platform/arch/host configs'' Jason said: "I would really appreciate any examples, or further advise anyone has." -> I heartily second that. A good start would be to fill in the cookbook, as Luke has been quietly whispering here and there. ;) Then my other main question at the moment is: what version

Puppet 2.7.7rc1 is available. This release fixes several issues with Mongrel and Puppet 2.7.x, Windows fixes and updates, test fixes, documentation updates and more. Release Notes for 2.7.7 series -- https://projects.puppetlabs.com/projects/puppet/wiki/Release_Notes This release is available for download at: http://downloads.puppetlabs.com/puppet/ See the Verifying Puppet Download section at:

I thought I had this fixed, but apparently not. It works okay from the console, but not from the view. I have the following: # partial schema create_table "users", :force => true do |t| t.string "login", :null => false t.string "first_name" t.string "last_name" t.string "email", :null => false

Puppet 2.7.8rc1 is available. 2.7.8rc1 contains everything that was being previewed in the 2.7.7rc series as well as some new content. Key highlight in this release (beyond items from 2.7.7rc series) are: * Allow providers to be selected in the run they become suitable * Showdiff is now not auto-enabled when running in noop mode * Provide default subjectAltNames while bootstrapping

Hiera 1.0.0rc3 is a feature release candidate designed to accompany Puppet 3.0. Changes to Hiera since 1.0.0rc2 were mainly to ease packaging and improve testing. Downloads are available: * Source http://downloads.puppetlabs.com/hiera/hiera-1.0.0rc3.tar.gz It includes contributions from the following people: Kelsey Hightower and Matthaus Litteken See the Verifying Puppet Download section at:

libswfdec/swfdec_as_object.c | 64 libswfdec/swfdec_file_reference.c | 2 libswfdec/swfdec_load_object.c | 81 libswfdec/swfdec_sprite_movie_as.c | 19 libswfdec/swfdec_system_security.c | 1 test/trace/Makefile.am | 72

Puppet 3.2.1-rc1 is a bugfix release candidate for the 3.x series of Puppet. This release addresses two major issues that were uncovered in 3.2.0 and caused us to pull that release (#20726 and #20742). It also includes a fix for Solaris support (#19760). Downloads are available at: * Source https://downloads.puppetlabs.com/puppet/puppet-3.2.1-rc1.tar.gz Available in native package format in

Hi, I am using the cloud provisioner to bootstrap some ec2 nodes, and these clients are signed using a randomly generated certname, which is put in /etc/puppet.conf at the bootstrap time (eg certname = d7bcd693-73fd-495f-0876-ff91ea11111e). But my puppet code repo also manages the puppet.conf file, so the file will be overwritten on the client at the first puppet run. Nevertheless, i should not

Hi, whenever i am starting puppet master after new installation it gives below messages .. /usr/lib/ruby/site_ruby/1.8/puppet/util/pidlock.rb:33:in `initialize'': Permission denied - /var/lib/puppet/run/master.pid (Errno::EACCES) from /usr/lib/ruby/site_ruby/1.8/puppet/util/pidlock.rb:33:in `open'' from /usr/lib/ruby/site_ruby/1.8/puppet/util/pidlock.rb:33:in

Facter 1.6.13 is a maintenance release in the 1.6.x branch with bug fixes. Downloads are available at: * Source: https://downloads.puppetlabs.com/facter/facter-1.6.13.tar.gz RPMs are available at https://yum.puppetlabs.com/el or /fedora Rubygem available at http://rubygems.org/gems/facter Debs are available at https://apt.puppetlabs.com Mac package is available at

Hello, I'm trying to set up, as explained in the wiki, shared mailboxes with symlink. I'm running dovecot-1.1.8 with LDAP pass/userdb. The Maildir layout goes like this : /courriel/boites/foobar : Maildir of user foobar (nfs) /courriel/meta/foobar : control files of user foobar (nfs) /var/dovecot/indexes : indexes (locally stored) I created : /courriel/boites/doveshared/.box/ :