similar to: ANNOUNCE: 0.23.2 is available

Hello everyone, I''m in the process of publishing a very small update release to Puppet, 0.22.3. Here''s the changelog: Fixed the authoconfig parameter so it is always defined. Enabling attribute validation on the providers that subclass ''nameservice'', so we can verify that an integer is passed to UID and GID. Added a downloadable

I''d like to be removed from the puppet-users email list... but I cant find my name on the webpage. Thanks, Jennifer Ford *********************************** Manager, Unix Administration Teach For America Phone: 212-279-2080 ext. 688 jennifer.ford at teachforamerica.org One day, all children in this nation will have the opportunity to attain an excellent education.

Hi all, I''m hoping to release 0.22.4 on Monday, so please test now. As always, if possible please actually run this somewhere in your infrastructure, in addition to running the unit tests, since there are always areas that aren''t quite covered with the unit tests. Hopefully this will be the last point release before the next major release (elmo). -- To my

Hi all, I think the 0.23.3 release is ready, with this changelog: Pulling the code related to the fixes for #896 from the 0.24.x branch. This provides support and workarounds for the security fix in Ruby that requires the server certificate naem to match the name the client is connecting to. Applied a few small fixes from the current 0.23.2 Debian package:

Hi all, As anyone on the commits list now knows, I''ve added all of the tags from svn to git. You can fetch all of the tags with this command: git fetch --tags Then you can compare the tagged releases like any other commit: git diff 0.23.1 0.23.2 I''ve also updated the PuppetSource wiki page with this info. -- Barondes'' First Law: Science abhors

OS: FreeBSD 6.2-RELEASE Puppet: 0.22.4 OS: CentOS 5.0 Puppet: 0.23.2 Is it currently not possible for puppetd to upgrade itself (0.22.4 -> 0.23.2)? I tried it, and when puppetd attempted to restart itself (using the init provider), it failed to start back up. Perhaps the init provider needs to close all file handles before executing the rc.d scripts? Additionally, I had puppetd update its

As mentioned, I''m making some changes to how I manage development around releases, since 0.23.2 still had too many bugs but it took me four months to get a release out. This is obviously unacceptable, regardless of how good my excuses are. :) The major change is that I''m always going to maintain a stable branch, named after the current stable minor release. For

I''ve published the tarballs and whatever bad packages my publishing system knows how to create; look for more official debs, sun packages, and rpms in the near future, hopefully. Note that this is mostly a bug-fix release, and I expect it to be a pretty painless upgrade for most everyeone (but please, test before upgrading). Here''s the changelog: Compile times now

FYI: We have a custom `checkout'' type which stopped working when migrating from 0.22.4 to 0.23.2-ish. This turned out to have been caused by the location of property.rb changing between 0.22.4 (puppet/type/property.rb) and 0.23.2-ish (puppet/property.rb). (I say 0.23.2-is because I''m using 40491ebe7ca9692b57fb533412ece8fb694b7d4c since it only has a few extra bugfixes over

I''ve just put it out; hopefully the packagers will get it in place soon. Here''s the changelog: Execs now autorequire the user they run as, as long as the user is specified by name. (#430) Files on the local machine but not on the remote server during a source copy are now purged if purge => true. (#594) Providers can now specify that some

Mr. Kanies, If you would not mind filing the bug, it would be appreciated. Puppet Version: 0.22.0 Platform: Fedora Core 6 Thank you, -- Rob -- ----- Original Message ---- From: Luke Kanies <luke@madstop.com> To: Puppet User Discussion <puppet-users@madstop.com> Sent: Friday, February 2, 2007 1:34:13 PM Subject: Re: [Puppet-users] Subscribe to multiple files - Modification On Feb

Hi all, Hobbeswalsh on IRC has discovered a backward compatibility issue in 0.24.0, preventing 0.23.x clients working well with 0.24.0 servers. Specifically, you can''t specify relationships to builtin resources when the client is 0.23.x, although specifying relationships to defined resources still works. The problem is that prior to 0.24.0 there was no central class

Hi all, I''ve just published the long-awaited new release of Puppet. Yes, I accidentally skipped 0.21.0; oops. Important features in this new release are: - Graphing Puppet now uses the GRATR[1] library to do all of the internals of managing relationships between resources. This gives Puppet a lot of functionality internally, but it also makes it possible to produce simple

hi all, we maintain about 30 puppet managed nodes. the version of the clients is 0.23.0 and 0.23.1. the master is 0.23.0. today we installed a new CentOS 5 node with David Lutterkort''s puppet 0.23.2 rpm. this host is a reinstall of an old FC4 on new hardware. we are getting this error on 0.23.2, never happened before: | Could not retrieve configuration: | Failed to parse template

Hi all, I''ve finally released 0.23.0 (only two days late!). You can get it from the usual locations (although the packagers will take a little while to package it up, I assume): https://reductivelabs.com/trac/puppet/wiki/InstallationGuide You can read the full changelog[1], which is pretty long, but here''s a summary of the things you either want or should look out for:

Hi all I''m working on my modular recursive Makefile & svn-backed home for my Puppet manifests, custom functions, types, etc. So I''m trying to put together individual modules, test targets and so on. I have noticed that the $libdir (and probably the other configuration options too) sources from puppet.conf are not overridden by specifying --libdir=blah on the commmand line

Hello all. I am using the munin module for a while now, I think that after the upgrade to puppet and puppetmaster 0.23.2 (or 0.23.1) it simply stopped working. Were there any changes to the realizing and exporting of resources? What could prevent this module from stopping to work. What happenes is that new hosts (munin::client nodes) do get stored in the database, but the munin::host does not

Hello everybody, I have updated the puppetmaster from 0.22.4 to 0.23.0 (and today to 0.23.2). Although ''dbmigrate=true'' is turned on AND the puppetmaster is saying it migrates the databse at startup, this does not happen. When it should store configs, I get the error: Could not store configs: Mysql::Error: #42S02Table ''database.resource_tags''

Hi, I''m running into a problem with the user type with puppet 0.20.1... this worked before with 0.19.x at least, not sure about 0.20. But I''ve got adduser.pp: <snip> define adduser($uid, $gid, $groups="users", $membership="minimum") { group { $name: gid => $gid, allowdupe => false, ensure

Hi all, Paul Anderson, a friend of mine who works at the University of Edinburgh, is looking for complicated problems that are currently difficult to handle with existing config mgmt tools. Please read his request below, and if you have any difficult problems that seem to meet his needs, I''d appreciate it if you would send descriptions of them to him. Thanks, Luke Begin