similar to: ANNOUNCE: 0.24.0 is out

I''ve now fixed all of the bugs I''m going to fix for 0.24.0/misspiggy. Please test that the current ''master'' branch in git works for you. I''ll probably release tomorrow, or maybe early on Thursday if I don''t hear of any show-stoppers. -- I don''t want any yes-men around me. I want everybody to tell me the truth even if it

Just started a "pilot" puppet server for real after messing around in VMs for the past week or so... I used the 0.24.0 since it was available, and on the test run, got this: err: Could not prefetch package provider ''yum'': Execution of ''/usr/bin/python /usr/lib/ruby/site_ruby/1.8/puppet/provider/package/yumhelper.py'' returned 512: /usr/bin/python:

Hi, I was managing a bunch of Centos 4.5 with Puppet until the ruby security patch bit me creating ssl problems. As I''m not able/willing to patch the installed version I tried upgrading to dlutter''s 0.24.0-2.el5 version. Unfortunately this didn''t help much. So I removed the server and client installation completely (making sure to manually remove the config, ssl, ...

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

On Wed, Aug 15, 2007 at 05:29:03AM -0000, puppet wrote: > #761: mount tries to mount an already mounted FS > -----------------------------+---------------------------------------------- > Reporter: porridge | Owner: luke > Type: defect | Status: new > Priority: normal | Milestone: misspiggy >

I just built new puppet rpm''s for Fedora (puppet-0.22.1-2) that fix the lockdir problem that many of you have encountered. The packages should show up on a mirror near you very soon. Unfortunately, I am having trouble getting to my buildsystem that I use for the RHEL versions of the RPM; I made the source rpm available on my people page[1] If you need the RPM for RHEL, you need to

Hi all, We''re getting close to release[1], so I''d appreciate it if people would start testing the current ''master'' branch with their repositories. I made quite a few internal changes, most of which shouldn''t even be noticed unless there are bugs, so just running a server and/or client under the current code would be a big help. I''m

Hi all, As promised, 0.24.1 is out. Here''s the changelog: Updated vim filetype detection. (#900 and #963) Default resources like schedules no longer conflict with managed resources. (#965) Removing the ability to disable http keep-alive, since it didn''t really work anyway and it should no longer be necessary. Refactored http keep-alive so

I see in the changelog that: You now must specify an environment and you are required to specify the valid environments for your site. (#911) Does this mean that the puppetmaster has to be updated before clients work correctly? I ask because I''m testing out a client upgrade to 0.24.0 (server is still 0.23.2) and this is what I''m seeing: [~]% sudo /foo/bin/puppetd

Hi all, I''m proud to announce that I seem to have pushed a new release of Puppet out in record time. This is a minor upgrade, mostly bugfixes and small features, but there are lots of each. See the changelog[1] for an idea of what this release provides, but keep in mind that this changelog is my first real attempt at keeping an up-to-date changelog. Enjoy! 1 -

Hi, I''m exploring Puppet and have hit a rather weird problem. The puppetmaster server is running CentOS4, fully updated, with puppet installed from the dlutter RPM repo, version 0.20.0-1.el4. I tried adding the remotefile function definition from http://reductivelabs.com/projects/puppet/documentation/installation.html in /etc/puppet/manifests/utils/remotefile.pp but when I start

Hi, everyone -- I downloaded puppet and have been playing with it. I''m using the RPM''s for RHE4 created by David (mentioned on the install page: http://people.redhat.com/dlutter/yum/rhel4/) with RHE''s ruby 1.8.1-7: ruby-1.8.1-7.EL4.8 ruby-libs-1.8.1-7.EL4.8 ruby-devel-1.8.1-7.EL4.8 I''m sure this is an easy one; all the same, I''m stumped. Please

The latest release is finally out; here is the changelog: Mostly a bug-fix release, with the most important fix being the multiple-definition error. Completely rewrote the ParsedFile system; each provider is now much shorter and much more maintainable. However, fundamental problems were found with the ''port'' type, so it was disabled. Also, added

Here at the University of Sydney I''m trying to give Puppet a go. I haven''t made it past first base yet unfortunately. We run RHEL 4 here, for the most part, and the install guide at http://reductivelabs.com/trac/puppet/wiki/InstallationGuide says that you should use the vendor''s Ruby, but Red Hat''s current version of Ruby is 1.8.1-07 - is this new

Just wondering if anyone has built (or found) Puppet rpm packages for RHEL4 x86_64 version. James ********************************************************************************* Important Note This email (including any attachments) contains information which is confidential and may be subject to legal privilege. If you are not the intended recipient you must not use, distribute or copy this

I''m receiving a "warning: Could not get config; using cached copy" when running "puppetd --test" with the latest puppet and puppet-server RPMs from dlutter''s site. Has anyone else seen this problem or can give me an idea of where to start looking for the problem? James *********************************************************************************

xf86-input-libinput 0.24.0 is now available. A couple of new features were added this cycle: * tablets now support a configurable pressure curve * tablets now have a 'area ratio' setting to be able to match the tablet aspect ratio with that of the screen * the mouse wheel's click angle now (correctly) affects how fast the scroll wheel triggers. In particular, if you have a wheel

I''m having some trouble with getting an ENC to work alongside site.pp: Even with a ''default'' node definition, and an ENC that only returns 0, regardless of input, consistently results in a ''cannot find node'' error. I''m wondering what I''ve missed here. I''ve tried to reduce everything to a ''base case'': and

Hi, When I run puppet agent --test --environment 42A, I have the following warning : Warning: Local environment: "42A" doesn''t match server specified node environment "production", switching agent to "production". ... The puppet manifest for the environment "42A" isn''t applied. The puppet version is 3.3.1-1puppetlabs1 on agent and

Hi- I recently upgrade from 0.24 to 0.25. In my 0.24 config, I had LDAP working such that Puppet was matching nodes in my directory to determine what classes to apply. I upgraded to 0.25 and this stopped working. I do not even see attempts from the Puppetmaster to search the directory (i.e., no connections to the ldap server). I *did* update the puppetmasterd conf, adding the variable