similar to: Puppet RPM's

Hi all Here is the 0.24.7 release - the last of the 0.24.x branch and codenamed Gonzo. You can download it here: http://reductivelabs.com/downloads/puppet/puppet-0.24.7.tgz Big tickets items in the release are: * Manifest documentation http://reductivelabs.com/trac/puppet/wiki/PuppetManifestDocumentation This new functionality creates documentation from marked up manifests and modules and

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

I have the latest kernel with the drivers for my 3ware 9550SX built in. Where can I find the tools and monitoring apps for this card? Are there rpms hiding somewhere, or do I need to build it from source? -- Bowie

Hello, I am trying to build an NTP v4.2.6p5 RPM using the instructions in the S4 how-to, however rpmbuild fails with the following error: error: File not found by glob: /home/thomas/rpmbuild/BUILDROOT/ntp-4.2.6p5-2.el6.x86_64/usr/share/man/man8/ntpdtime.8* RPM build errors: File not found by glob: /home/thomas/rpmbuild/BUILDROOT/ntp-4.2.6p5-2.el6.x86_64/usr/share/man/man8/ntpdtime.8* I

Hello All, In all the examples that I see you configure one repo per file; i.e: yumrepo { "testing.com-repo": baseurl => "http://repos.testing.com/fedora/$lsbdistrelease/", descr => "Testing.com''s YUM repository", enabled => 1, gpgcheck => 0, } But how do I specify multiple entries to the same file?. For instance, I just one to have one

Hi, I am trying to do my first puppet configuration, already installed the puppetserver and client, in this link show my configuration and my puppet structure: http://paste.pocoo.org/show/212227/ But when i run the client side daemon i get this message: info: /Class[main]/Node[basenode]/Class[inittab]/File[inittab]/source: No specified sources exist err:

Hi, A critical regression has been discovered in e2fsck. The problem was introduced in upstream 1.41.5 and is causing updates to block group descriptors to be lost after journal replay. Our 1.41.5.sun2 (.sun1 too) e2fsprogs version also suffers from this problem. We are working on rebasing our e2fsprogs package on 1.41.6 (see bug 19852). Until the new rpm is available (should be very soon), we

Hi, A critical regression has been discovered in e2fsck. The problem was introduced in upstream 1.41.5 and is causing updates to block group descriptors to be lost after journal replay. Our 1.41.5.sun2 (.sun1 too) e2fsprogs version also suffers from this problem. We are working on rebasing our e2fsprogs package on 1.41.6 (see bug 19852). Until the new rpm is available (should be very soon), we

hello list, I'm trying to build a postfix rpm that has mysql support included. I've found the line where I need to define mysql support but it seems that I am being tripped up by some build dependencies: [root at beta SPECS]# rpmbuild -ba postfix.spec error: Failed build dependencies: MySQL-shared is needed by postfix-2.9.1-1.rhel5.x86_64 MySQL-devel is needed by

NSD 2.3.2 is a bugfix release. Please see the README document for configuration and installation instructions. You can download NSD from http://www.nlnetlabs.nl/nsd/ Note: we switched to SHA-1 for tarball digest. 2.3.2 ============= FEATURES: - Bug #101: add support for the SPF record. BUG FIXES: - Bug #100: replaced non-portable use of timegm(3) with portable

What''s the correct yum repo to use for installing Puppet & Facter on RHEL5 and Centos5? I used to get them from the dlutter-rhel5 repo but this seems to be massively out of date now - latest version of puppet-server in there is 0.24.5-1.el5 and facter 1.5.4-1.el5. In Epel I see puppet-server 0.24.8-1.el5.1 and facter 1.5.4-1.el5 which is better but isn''t 1.5.4 the version

Hi, I am using puppet (version 0.25.5-1.e15 for redhat) for password management for non-system users. This morning, users on some of my puppet clients had their encrypted password strings in /etc/shadow replaced with the following string: YAML::syck::BadAlias That has effectively broken the users'' ability to login to those servers. Puppet will not overwrite that string with the

Hi, When you set managehome to false on a User ressource, homedir will still be created on a CentOS box as the -M flag is not passed to useradd. $ diff -u /usr/lib/ruby/site_ruby/1.8/puppet/provider/user/ useradd.rb.bak \ /usr/lib/ruby/site_ruby/1.8/puppet/provider/user/useradd.rb --- /usr/lib/ruby/site_ruby/1.8/puppet/provider/user/ useradd.rb.bak 2008-10-23 01:19:07.000000000 +0200

All too quickly we''re back with a maintenance release: 2.6.3. This release addresses some issues in the 2.6.2 release. 2.6.3 is a maintenance release in the 2.6.x branch and it contains only bug fixes and no new features or other changes. The release candidate is available for download at: http://puppetlabs.com/downloads/puppet/puppet-2.6.3rc1.tar.gz Please note that all final

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Puppet 0.25.1 - code name "zoot" - is now available. The 0.25.1 release is a maintenance release in the 0.25.x branch. The release is available at: http://reductivelabs.com/downloads/puppet/puppet-0.25.1.tar.gz http://reductivelabs.com/downloads/gems/puppet-0.25.1.gem Please report issues and feedback via the Reductive Labs Redmine site:

I''m using puppet-0.24.8-4.el5 on CentOS 5.4. My problem is yumrepo isn''t writing the "name=" field to the repository files which causes yum to complain with the error: Repository ''local-CentOS-5.4-x86_64'' is missing name in configuration, using id I get this behavior on all of my yumrepo definitions. One of them looks like this: yumrepo {

Hello, I want to use exported resources (namely sshkey) and with the following code, each node gets his own ssh key written into /etc/ssh/ssh_known_hosts, but not the others ones. This is with puppet 0.24.7 on redhat. node ''node1'' { @@sshkey { "node1": type => rsa, key => $sshrsakey } Sshkey <<| |>> } node ''node2'' {

On 18/05/16 16:16, Markus Dellermann wrote: > Hi, > Am 18.05.2016 um 15:39 schrieb Robert K. Nelson: >> We are using samba4 as an AD controller under OpenSuSE 13.2 using the >> repository at: >> >> http://download.opensuse.org/repositories/network:/samba:/TESTING/openSUSE_13.2 >> >> > Not related to your Problem, but are you sure, that this repo really

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