similar to: ANNOUNCE: New development/release practices

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

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 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, I released 0.23.2 last night; you can get it from the usual places [1]. Apparently Matt has already uploaded debs. This is a bug-fix release, and I''m hoping it will be stable enough to supplant 0.22.4. It looks pretty likely that I''ll be putting out another release very soon, though, because a coworker of Matt''s has figured out a way to use HTTP

Looks like there''s enough interest in runnels that it''s time to create a list: https://mail.madstop.com/mailman/listinfo/runnels-dev -- Risk! Risk anything! Care no more for the opinions of others, for those voices. Do the hardest thing on earth for you. Act for yourself. Face the truth. -- Katherine Mansfield

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

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, 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, 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

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 >

Hi all, Now that it looks like we have some kind of process to manage tickets, I need people to help me with that process. There are currently something like 117 open tickets, and there are about 6 different dimensions on which these tickets can be categorized (e.g., complexity, triage stage -- all the report times listed on the Reports page). My plan is to work my fingers raw going

Hi all, As requested by at least one person (and because I''d been thinking about it and figured it would be a good idea), I''ve just made it simple to use external node sources with Puppet. If you set ''external_nodes'' to a command (the default is ''none''), then Puppet will call that command and use it to configure nodes. The output of

Hi all, I''m happy to announce that Puppet''s latest release is out now. This release provides a mostly refactored interpreter, which provides two key language features. First and foremost, we now have virtual resources[1], which allows you to specify resources in one part of your configuration and mark them to be sent to your client in another. Second, resource overrides

Hi, I''m a new puppet user (thanks !) and I''m just looking at moving my homegrown manifest structure into something resembling the best practise guide at : http://www.reductivelabs.com/trac/puppet/wiki/PuppetBestPractice. It seems as if the structure here doesn''t map to the default puppet layout (and thus doesn''t work with the standard puppet config

Hi all, Is everyone switched over to the Google lists? I''m basically ready for the switch, I think, and doing so would be one more closed loop for me. I notice we''ve only got a bit over 300 subscribers to the Puppet Users list, while my madstop list has nearly 600. This is a bit depressing, but it probably represents a better idea of who''s actually using the

Hi all, I''ve now got all but one bugs closed or bumped to the next release, and I am planning on releasing today. People have been testing the SVN code all week and have helped to find many bugs that we would not have wanted in a released project, and you can help more by testing right now. The major change in this release is that the transactions now use a graph library to

OK, too bad. I could work around it of course by adding ''unless'' and ''creates'' clauses on all the individual parts of the define where appropriate, but I think I''ll just ignore the warnings and overhead for now. It would be cool, though, if something like the ''unless'', ''onlyif'', etc, logic was available for all

Hi, I''m experimenting with using Mongrel to serve XMLRPC, and I''m having trouble passing the XMLRPC errors on to the client. In my webrick implementation, I just raise the XMLRPC error and the client receives it and can handle it like a normal exception. With Mongrel, when I raise the error, Mongrel catches it and just closes the client connection, which means the

Hi all, I''ve now finished all of the functionality I plan to add in the next release, so all that remains is closing as many open bugs as possible. I''ve gone through and marked all of the bugs I specifically plan on fixing with the ''minor'' milestone. If you have a bug in the db[1] that you think needs to be fixed in the next release but is not

Hi all, I''ve just rewritten the Puppet introduction from scratch: https://reductivelabs.com/trac/puppet/wiki/PuppetIntroduction I think it''s better, but I''m not convinced it''s a whole heckuva lot better. Comments are very much appreciated, especially if you can recommend a better approach to the document. I tried to organize it how I have been giving