similar to: [Puppet-dev] 0.23.3 release

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, I''m getting a "Could not retrieve dependency" error and I can''t figure why. Someone got a cluestick for me? I''m using the following simplified configuration to ensure sshd is running and gets reloaded when the config file changes: ---- site.pp ---- import "classes/sshd.pp" node obsd42 { include ssh-server } node debian40 { include

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

https://bugzilla.samba.org/show_bug.cgi?id=6067 Summary: IPv6 literal addresses broken Product: rsync Version: 3.0.4 Platform: Other OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: arekm@maven.pl QAContact:

Hi all, It was brought to my attention that the front page lists 0.23.3 as the stable release, but that no such release exists. I could have sworn I released this a few weeks ago, but now I can find no evidence of that. I''m going to publish it from the latest commit in the 0.23.x branch as soon as possible (probably in about 12 hours), so if anyone wants to get that last-minute

Greetings, Shouldn''t puppetd -o --ignoreschedules ... imply that splay* options are ignored :-) If that''s not the intended behavior could we get a --run-now that ignores splay* and schedules? Cheers, Ryan

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:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Klaus Ethgen wrote: > > Behind the line it was more problematic to get to the informations about > the bug tracker and the knowledge to apply to this mailing list with a > non-google address than it is needed and more than it is common with > other software projects. And that was, beside the bug, the main subject > of that thread.

Hi, I have a centOS with puppet-server : puppet-server-0.24.0-2.el5 First of I have to say that ever since I installed puppet-server-0.24, I''m unabble to run the puppetmasterd with de flag -d, the programs goes always to daemon mode, with no debug output. Second issue is related with debian clients with puppet-0.20.1-1, that when I have a service subscribed to a file returns always the

At long last, 0.24.0 has been released. Look for your friendly packagers to package it up in the near future, but in the meantime you can download it: http://reductivelabs.com/downloads/puppet/puppet-0.24.0.tgz I''ll be walking the different release sites (RubyForge et al) and posting it there, too. Look for a related announcement later today on changes in development practices

So I''ve done some Mac OS X pkgs for the latest Facter and Puppet, as well as a combined mpkg for them both. Jeff McCune and I are doing a fair bit of testing on them this week in preparation for MacWorld, so I wasn''t going to upload them to the official site for another few days, but they''re looking pretty good. http://explanatorygap.net/puppet/Facter_1.3.8.pkg.zip

While upgrading to 0.24.1 i encountered some dependency failures. It can be reproduced with the following snippet. file { "puppet-test": path => "/tmp/puppet.test", ensure => file } exec { "/bin/true 1": require => File["puppet-test"] } exec { "/bin/true 2": require => File["/tmp/puppet.test"] } 0.23.2 handles

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

I just upgraded from 0.23.2-1 on RHEL 4&5 to 0.24.1-1. I used Dlutter''s repository. What a mess I''m in now. Anyway to make a long story short I moved all of the old configs out of the way (/etc/puppet, /var/lib/puppet) and started over with a fresh install. I can''t get puppetd on the server to request a cert. If I do a "puppetd -v --waitforcert 90" the

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Puppet 0.24.8 is now available! This is a maintenance release for the 0.24.x branch but contains a small number of new features including some significant performance enhancements for large installations and stored configurations. The tarball is available at: http://reductivelabs.com/downloads/puppet/puppet-0.24.8.tgz MD5 hash:

Hi working with the following puppet-0.24.1-1 puppet-server-0.24.1-1 ruby-1.8.1-7.EL3.8 rhel3 u8 The puppetmaster is running on rhel4 u5 I am working with puppet and rhel3 u8 and I have any an issue anytime I ask puppet to interact with yum for the record - yum from the cli works perfectly I setup a class to manage ntpd and in the class I have the following function # make sure ntpd is

Hi all, I''ve just installed puppet in my ubuntu gutsy 7.10 linux using gem: # sudo gem install puppet Then, I made a basic site.pp manifest and following the InstallationGuide I ran: $ sudo puppetmasterd --mkusers Could not configure for running; got 1 failure(s) What error? I managed to get an error message on /var/log/daemon.log Jan 30 16:22:13 acero puppetmasterd[13800]:

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,guys I''m test the resources export and collect , OS is Debian etch and sarge, puppet server and client version all of the 0.23.2 ; the db is MySQL-4.1 My test code is like this. node ''b'' { @@file {"/tmp/a": ensure => present ,content => "test"; } } node ''a'' { File <<||>> } I run puppetd on

Hi Just wondering if Virtual Folder functionality was on the roadmap for Dovecot? Thanks James Turnbull -- James Turnbull <james at lovedthanlost.net> --- Author of Pro Nagios 2.0 (http://www.amazon.com/gp/product/1590596099/) Hardening Linux (http://www.amazon.com/gp/product/1590594444/) --- PGP Key (http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x0C42DF40) --------------