similar to: gem provider and alternate Ruby installs

int he example below I run facter looking for the fact "sp_serial_number". as you can see, the command facter sp_serial_number returns nothing, but the fact is there and is returned when just running facter and grepping for the fact. Some fact seem to work and others do not. any ideas? marcuspro:~ allan$ facter --version 1.5.7 marcuspro:~ allan$ facter sp_serial_number marcuspro:~

Hi, we want to install the ruby-gem package on a Debian system using puppet. package { ''ruby1.9.1'': ensure => present } In another manifest we want to use the gem provider to install a ruby gem. package { ''bundler'': ensure => present, provider => gem } On the first run the puppet agent run checks for a functional gem binary on the system. It will

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

Hey everyone, I''m experiencing an issue resulting from the way RubyGems works when dealing with multiple gem versions. When managing a gem through the Package provider, setting ensure to a version lower than a currently installed version will result in Puppet installing the older version, however RubyGems will also keep the newer version, and this newer version will remain the default.

Hey all, I''m not sure if there''s a real issue or if I''m doing something incorrectly. I have a custom compiled gem that I''m installing via: package { "sapnwrfc-0.24": ensure => ''installed'', provider => ''gem'', source =>

Hey folks, I''ve looked through the docs, and the mailing list, but for the life of me I can''t figure out how to specify an alternate gem repository for a package. From the docs, it looks like I should be able to do source => whatever, but this seems to just send gem looking for a specific gem at a url, rather then the more general alternate source for the gem. It looks

Greetings, I''ve two questions for y''all. 1) I''ve setup an alternate installation path for puppet in a site local directory outside of ''the usual places''. Puppetd seems to insist that /etc/puppet/namespaceauth.conf exists despite setting :authconfig in both puppet and puppetd. As a result part of my installation now includes a symlink to point

I''m trying to have puppet install a bunch of ruby gems for me, but I''m running into problems with a few of them. This is on CentOS 4.4, ruby 1.8.5 (2006-08-25) [x86_64-linux] and the latest puppet from svn as of yesterday afternoon. I have: package { fastthread: ensure => "0.6.4.1", provider => gem, require =>

Are there any good guides out there to using Puppet agents with a dedicated, separate ruby install? Our apps are all Ruby based and require different versions than Puppet. Installing the agent from a package will override our ruby installs. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit

*Note, I''m very green when it comes to ruby development.. I''ve created a couple of custom providers and types, both of which rely on a particular ruby gem in order to function. How should I go about ensuring the gem dependency on the puppet clients before puppet syncs the plugins (the broken ''require'' in the provider will cause puppet to exit during a run)? On

What is the right path for ruby gems on puppet master. Scenario: I have installed hiera couple of months back. So the gem was installed under /opt/puppet/lib/gems/1.8/gems/hiera-0.3.0 /opt/puppet/lib/gems/1.8/gems/hiera-puppet-0.3.0 Later when I updated to new version of hiera then it installed (via gem install) under /opt/puppet/lib/gems/1.8/gems/hiera-1.1.1

All, Trying to install puppet-2.6.3 on CentOS 5.4 and I get the following. [root@stsdev-pri ~]# gem install puppet-2.6.3 ERROR: http://rubygems.org/ does not appear to be a repository ERROR: Error installing puppet-2.6.3: puppet requires facter (>= 1.5.1, runtime) Facter is installed: [root@stsdev-pri ~]# facter -v 1.5.8 Ruby is installed: [root@stsdev-pri ~]# ruby --version ruby

Hiera was properly working in my environment. But puppet was looking at old version even when I have the latest hiera gem installed. So I could''nt use json backend. But puppet is not looking at my latest hiera gem. Not sure when went wrong here. Scenario: I have installed hiera couple of months back. So the gem was installed under /opt/puppet/lib/gems/1.8/gems/hiera-0.3.0

I got puppet installed and running on Redhat 8 today. I''m passing on my notes to the list to help out others that may want or need puppet running on older Redhat servers. This is pretty much a copy & paste from my own personal wiki so please forgive any odd formating. ==== Puppet Setup on Redhat 8 ==== Here''s a quick-n-dirty on how I got puppet running on redhat 8.

I have installed puppet 3.0.1, passenger 3.0.18 and ruby 1.9.3 and have hit errors. The error I am hitting is this: Error message:cannot load such file -- puppet/util/command_lineException class:LoadError I get this when hitting the puppet server using https://puppetserver:8140 If I use ruby 1.8, everything works. This is a new deployment so I would like to use ruby 1.9.3 rather than the

i am not a specialist of gem installs but is it possible to do a gem upgrade with a distant package ? i tried but it allways failed to upgrade puppet. I intall the new version and then uninstall the old one... any better idea ? -- Cordialement, Ghislain _______________________________________________ Puppet-users mailing list Puppet-users@madstop.com

Hi, I have a problem with augeas, puppet and Suse 10 SP2. Augeas works when I use the augtool to edit files. But I would like to use it in combination with puppet. My class looks something like this: augeas {"sysctl.conf": provider => "augeas", context => "/files/etc/sysctl.conf", changes => [ "set

Hi, I think this has been discussed previously on the list, so apologies if I''m covering old ground but I''ve been using puppet to manage a few Rails applications which have dependencies on quite a few gems, so it''s getting to be a bit of an onerous task to manage them. It looks like the command line interface to gems doesn''t really support automated

I am running puppet 2.7.9 and using the pip provider. The package gets/is installed but puppet installs it on every run. Do other people run into this. I tried search bugs and the group and have not seen any mention of it. Chris -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to

Hi. While not directly related to this list, I''m quite stuck on this. When trying to compile the mysql gem, I''m getting this error: -bash-3.2# gem install mysql Building native extensions. This could take a while... ERROR: Error installing mysql: ERROR: Failed to build gem native extension. /usr/bin/ruby extconf.rb install mysql checking for mysql_ssl_set()... no