Re: [Puppet Users] support on rhel / epel
augeas comes from the rhel optional channel. You'll have to enable that. On Wed, May 16, 2012 at 12:13 PM, Tim Coote tim.coo...@googlemail.com wrote: Hullo I'm trying to install puppet on some rhel 6.2 boxes, which have epel repo installed. However, I'm getting dependency errors for augeas- libs: Error: Package: ruby-augeas-0.4.1-1.el6.x86_64 (epel) Requires: augeas-libs = 0.8.0 Installed: augeas-libs-0.7.2-6.el6.x86_64 (@rhel-x86_64- server-6.1.z) And I cannot google any other instances of this issue. epel doesn't carry augeas-libs, so I'm not very clear on how it manages to carry puppet, which depends on it. Any thoughts? Tim -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- Nathan Powell Linux System Administrator This machine kills fascists ~ Woody Guthrie -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] 32bit and 64bit version of a package
On Thu, Feb 23, 2012 at 5:57 PM, Alan Laird a...@laird.net wrote:
I'm trying to write a recipe to install the latest libstdc++ in both
32bit and 64bit flavors and running into issues. Yum only wants to
install the 64bit version if I do:
yum install libstdc++
If I do something like:
package { libstdc++.i386 : ensure = latest }
It tells me nothing to do
What does it say if you do:
sudo yum -q install libstdc++.i386
--
Nathan Powell
Linux System Administrator
Now I see it clearly. My whole life is pointed in one direction. I
see that now. There never has been any choice for me. ~ Travis Bickle
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Sorted hash in template example
On Thu, Feb 23, 2012 at 5:20 PM, Jared Curtis ja...@shift-e.info wrote:
Does anyone have a better solution?
Better? I dunno. But an array of hashes will do what you want as well.
dbs = [{:foo = 'bar'}, {:hai = 'bai'} ]
dbs[0] etc.
--
Nathan Powell
Linux System Administrator
Now I see it clearly. My whole life has pointed in one direction. I
see that now. There never has been any choice for me. ~ Travis Bickle
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: Problem with Custom Facter
On Tue, Feb 21, 2012 at 9:57 AM, jcbollinger john.bollin...@stjude.org wrote: Alternatively, `yum -q check-update | grep '\\w' | wc --lines`.chomp Yep, lots of ways to do it. sudo is not needed to run yum queries, and avoiding sudo when you don't need it is good practice. Personally, I find that command a lot Good point. I was testing in irb as a regular user and just cut and paste what I did into the email. It shouldn't have sudo in there. more legible than the Ruby split / reject / length business, too, though YMMV. I think method chaining and the functional aspects (reject) of Ruby are elegant and use them every chance I get. Both are fine and valid though. -- Nathan Powell Linux System Administrator Where else would you rather be than right here, right now? ~ Marv Levy -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Problem with Custom Facter
On Mon, Feb 20, 2012 at 5:33 PM, Matt Mencel m...@techminer.net wrote: The output I get back in my fact reports only contains a string with updates in it, so no number. However, if I paste the code inside the setcode block into a test.rb scriptit works just fine. Are you testing this code on the same version of EL that you are deploying to? AFACT #lines wasn't added until 1.8.7 and if you are deploying to EL5 you don't have that. -- Nathan Powell Linux System Administrator Where else would you rather be than right here, right now? ~ Marv Levy -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Problem with Custom Facter
On Mon, Feb 20, 2012 at 5:33 PM, Matt Mencel m...@techminer.net wrote:
I am trying to write a custom facter for CentOS/RHEL that tells me how many
updates are found on a run of 'yum check-update'
Sorry I replied hastily. After replying I thought about what you're
trying to do. You don't need all those gyrations to get this data
Tested quickly on RHEL6 and CentOS5:
`sudo yum check-update -q`.split(/\n/).reject{|i| i == }.length
--
Nathan Powell
Linux System Administrator
Where else would you rather be than right here, right now?
~ Marv Levy
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
