Red Hat Bugzilla – Bug 861617
puppet --parseonly broken (ruby 1.9.x issue)
Last modified: 2013-03-20 09:28:00 EDT
Description of problem:
See upstream bug http://projects.puppetlabs.com/issues/16445
$ puppet --parseonly
/usr/share/rubygems/rubygems/custom_require.rb:36:in `require': iconv will be deprecated in the future, use String#encode instead.
Could not parse options: wrong number of arguments (1 for 0)
Version-Release number of selected component (if applicable):
Upstream has closed the bug as wontfix, as they don't support the version of ruby we have. I understand that puts us in a hard place, but I think we need a solution here.
I'm not sure I see a good way out of this. It's unfortunate that --parseonly was removed upstream and it's unfortunate that 1.9 made it into f17 leaving us with no choice but to update puppet to 2.7 before we wanted to do so. At this point in f17's life, I'm not sure that it's something that is worth the effort to fix. 3.1 is in f18+ and that should resolve the issue.
Actually, I didn't look closely enough at this. Using --parseonly is unsupported in 2.7, so that's not something we will support in our packages. You should use puppet parser validate [<manifest>] [<manifest> ...] instead, as the 2.7 release notes suggest¹.
The iconv warning is going to be fixed with a few backported patches from the 3.x branch upstream. That is already filed and tracked in bug #809911. I am closing this as a duplicate of that bug, as the only valid bug here is that warning.
Sorry for the long delay.
*** This bug has been marked as a duplicate of bug 809911 ***