ncy: /usr/bin/ruby for package:
> puppet-3.4.2-1.el6.noarch
>
> Since neither were found in the RPM DB it installed Ruby 1.8.7 for you.
>
>
> On Tue, Jan 21, 2014 at 1:14 PM, machete >
> wrote:
> >
> >
> > On Tuesday, January 21, 2014 3:13:49 PM UTC-5, m
On Tuesday, January 21, 2014 3:13:49 PM UTC-5, machete wrote:
>
> The 1.8.7 ruby, rubygems and its gems were uninstalled. The root .gem and
> user .gem directories were also removed. I am hunting for what I am
> overlooking.
>
> I am now looking at using the yum package
The 1.8.7 ruby, rubygems and its gems were uninstalled. The root .gem and
user .gem directories were also removed. I am hunting for what I am
overlooking.
I am now looking at using the yum package to install puppet. Listed below
are the results of the package install. Notice it's trying to ins
-terminus-1.0.gem
And puppet master starts now.
On Thursday, December 5, 2013 1:51:05 PM UTC-5, machete wrote:
>
> *using sudo:*
> ~> sudo puppet apply -e 'file { "/tmp/adhoc": content => "Written from
> puppet on $hostname\n" }'
> Error: Cached fac
*using sudo:*
~> sudo puppet apply -e 'file { "/tmp/adhoc": content => "Written from
puppet on $hostname\n" }'
Error: Cached facts for awsomepuppet failed: Could not find terminus
puppetdb for indirection facts
Error: Could not run: Could not retrieve facts for awsomepuppet: Could not
find te
*using sudo:*
~> sudo puppet apply -e 'file { "/tmp/adhoc": content => "Written from
puppet on $hostname\n" }'
Error: Cached facts for awsomepuppet failed: Could not find terminus
puppetdb for indirection facts
Error: Could not run: Could not retrieve facts for awsomepuppet: Could not
find te
*using sudo:*
~> sudo puppet apply -e 'file { "/tmp/adhoc": content => "Written from
puppet on $hostname\n" }'
Error: Cached facts for awsomepuppet failed: Could not find terminus
puppetdb for indirection facts
Error: Could not run: Could not retrieve facts for awsomepuppet: Could not
find te
using your new ruby
> 1.9.3 gem executable will cause the new puppet gem (and all new 1.9.3
> rubygems) to use ruby 1.9.3. Note that unless you remove them, your
> 1.8.7 ruby, rubygems, and all 1.8.7 installed gems will still exist.
>
> On Wed, Dec 4, 2013 at 12:33 PM, mac
Wednesday, December 4, 2013 3:31:26 PM UTC-5, machete wrote:
>
> Hey Moses,
>
> Thanks for the quick response.
>
> Puppet was install via ruby gem ... I know, but it is so easy.
> Ruby/rubygem are running from source.
> OS is CentOS 6.4 Linux puppetdb 2.6.32-71.el6.x86_64 #1 SM
, 2013 3:22:56 PM UTC-5, Moses Mendoza wrote:
>
> How did you install puppet originally? Are you running from packages,
> rubygem, or running from source, or some other method?
>
> On Wed, Dec 4, 2013 at 11:58 AM, machete >
> wrote:
> > Hey what gives ... ? ;)
> >
Hey what gives ... ? ;)
I've got a shiny new install of ruby 1.9.3-p484 ... and my 'sudo puppet
resource package puppetdb ensure=latest' loads ruby 1.8.7
Would someone please point me to the instructions ( or share ) on how to
get my 'sudo puppet resource package puppetdb ensure=latest' t
Sorry if that was a vague request .. Here is some more details on the
env...:
~> ruby -v
ruby 1.9.3p484 (2013-11-22 revision 43786) [x86_64-linux]
~> puppet -V
3.3.2
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this gr
Hey what gives ... ? ;)
I've got a shiny new install of ruby 1.9.3-p484 ... and my 'sudo puppet
resource package puppetdb ensure=latest' loads ruby 1.8.7
Would some please point me to the instruction ( or share ) on how to get my
'sudo puppet resource package puppetdb ensure=latest' to
If you have used a public accessible manifest for ruby 1.8.7 ree or
you are willing to share ... I am looking for one!
Oh, and i've not yet acquired the skillz to create my own. But when I
do, I promise to share. ; )
T.
--
You received this message because you are subscribed to the Google G
14 matches
Mail list logo
