Description of problem:
Seeing this trying to run puppet:
/usr/share/rubygems/rubygems/custom_require.rb:36:in `require': iconv will be deprecated in the future, use String#encode instead.
Version-Release number of selected component (if applicable):
Well, this is issue of Puppet with Ruby 1.9.3.
$ grep -r 'require.*iconv' *
$ grep -r 'require.*iconv' *
lib/puppet/external/pson/pure.rb: require 'iconv'
I am reassigning this issue to puppet component. However I doubt that puppet maintainer will do anything about it ATM, since it is just warning. Nevertheless, iconv was already removed from Ruby 2.0 , hence the upstream should definitely do something about it.
Reported upstream in Puppet:
this is biting openshift-origin-msg-node-mcollective as well: minutely generated mails. that is mildly annoying.
there is a fix in  (unfortunately i do not know how to link to the actual diff), that can easily be backported. according to the upstream report the fix will only be released with puppet 3.0. is this patch acceptable?
I have created package which adds two patches from upstream to fix the issue here and an additional problem:
/usr/share/ruby/vendor_ruby/puppet/provider/service/bsd.rb:12: warning: class variable access from toplevel
srpm, spec and patches available here:
*** Bug 861617 has been marked as a duplicate of this bug. ***
puppet-2.7.21-2.fc17 has been submitted as an update for Fedora 17.
Thanks for the patch links Terje and Tobias. That saved me a lot of time!
Sorry it took so long to get this fixed.
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing puppet-2.7.21-2.fc17'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '17'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 17's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 17 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged change the
'version' to a later Fedora version prior to Fedora 17's end of life.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Still not pushed to stable?