On Tue, Nov 27, 2012 at 3:53 PM, Alaric <paxindust...@gmail.com> wrote: > > Swing and a miss... even after verifying and manually removing any gems, and > any cached gems, reinstalling effected packages and verifying, I still get > the same error...
Are you able to reduce this down to a specific module or class that triggers this issue? I've now got a fresh centos 5.8 VM with an out of the box puppet-3.0.1 install on it with all dependencies met via puppetlabs' repo. I can't trigger it with a simple module, but am willing to try to reproduce it for you. Thanks, Matt. -- 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.
