The Puppet Labs Issue Tracker has Moved:

This issue tracker is now in read-only archive mode and automatic ticket export has been disabled. Redmine users will need to create a new JIRA account to file tickets using See the following page for information on filing tickets with JIRA:

Bug #7648

Module tool does not work with Ruby 1.9

Added by Jacob Helwig almost 5 years ago. Updated almost 5 years ago.

Status:ClosedStart date:05/24/2011
Priority:NormalDue date:
Assignee:-% Done:


Category:-Spent time:-
Target version:-
Keywords: Affected URL:

We've Moved!

Ticket tracking is now hosted in JIRA:


As reported by Kevin Beckford on the mailing list

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
  * 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)


#1 Updated by James Turnbull almost 5 years ago

  • Status changed from Unreviewed to Closed
  • Assignee deleted (Igal Koshevoy)

This is actually an issue with Puppet 2.6.8 NOT puppet-module. It’s fixed in the forthcoming 2.7.0 release which will support Ruby 1.9.2 and later.

Also available in: Atom PDF