Jira (PUP-3190) "each" no longer supported in Puppet 3.7.0

[Per Cederqvist (JIRA)]

Title: Message Title

Per Cederqvist commented on an issue   Re: "each" no longer supported in Puppet 3.7.0 I applied the proposed patch on top of my installed Debian package, and now Puppet seems to work again! A big thank you! In case anybody else has this issue, here is what I did on a Debian system: cd wget https://github.com/zaphod42/puppet/commit/0447ea0271966703c246e945a5d9e1d6c6d7e5b0.patch cd /usr/lib/ruby/vendor_ruby patch -p2 < ~/0447ea0271966703c246e945a5d9e1d6c6d7e5b0.patch The changes to the three files in lib/puppet/pops/loader applied cleanly. The changes in spec/unit could not find any file to patch, presumably because the unit tests are not included in the Debian package; I just skipped those files. After restarting apache2 (I'm running the puppetmaster under Passenger) everything started working. Add Comment   Puppet / PUP-3190 "each" no longer supported in Puppet 3.7.0 After upgrading to Puppet 3.7.0, the puppetmaster no longer recognizes the "each" keyword. It prints this in the log: {noformat} Sep 5 19:22:56 minicfg2 puppet-master[11897]: each() is only available when parser/evaluator future is in effect on node buildhost1.lysator.liu.se {noformat} The /etc/puppet/puppet.conf on the puppetmaster host looks ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.