I shall try this inquiry again:

I installed the puppet module tool version 0.3.3 locally to my laptop.

I have installed ruby 1.9.2 on the laptop.  Surely by now, puppet and facter 
work with ruby 1.9.2?  They certainly seem to work well.

I have installed ruby using macports, and am using the +nosuffix option, 
which installes ruby as 'ruby' not 'ruby19'


I have attached the output from my attempt to run this tool to this message. 
 It appears as if there is a ruby error in puppet 2.6.8?  I'm unsure. 

Pls advise.

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

Fetching: puppet-module-0.3.3.gem (100%)
******************************************************************************

  Thank you for installing puppet-module from Puppet Labs!

  * Usage instructions: read "README.markdown" or run `puppet-module usage`
  * Changelog: read "CHANGES.markdown" or run `puppet-module changelog`
  * Puppet Forge: visit http://forge.puppetlabs.com/
  * If you don't have Puppet installed locally by your system package
    manager, please install it with:

        sudo gem install puppet


******************************************************************************
Successfully installed puppet-module-0.3.3
1 gem installed
Installing ri documentation for puppet-module-0.3.3...
Installing RDoc documentation for puppet-module-0.3.3...
[root:8va:0:~ ]# rehash        
[root:8va:0:~ ]# puppet-module usage
/opt/local/lib/ruby1.9/gems/1.9.1/gems/puppet-2.6.8/lib/puppet/util/log/destinations.rb:99:
 warning: class variable access from toplevel
/opt/local/lib/ruby1.9/gems/1.9.1/gems/puppet-2.6.8/lib/puppet/application/kick.rb:
 
/opt/local/lib/ruby1.9/gems/1.9.1/gems/puppet-2.6.8/lib/puppet/application/kick.rb:107:
 Invalid next (SyntaxError)

Reply via email to