Bug#680606: Run time stderr warnings with puppet and ruby1.9.1
Package: installation-reports
Severity: normal
Dear Maintainer,
I downloaded and installed Debian wheezy installer alpha 1
(LXDE-CD-installer-disk) on one test server and also on my Asus 1001-PX laptop.
On the server, I did a minimal installation and on the laptop I selected the
default base packages, and selected laptop during the installer phase.
The overall process worked out as expected.
The server is managed by puppet (2.7.17-1) from my laptop (puppet-server).
The pupppet-agent on the server is not daemonized. I use cron or the cli.
I did not expect to see 'stderr warning' messages to stdout like so:
# puppet agent --no-daemonize --onetime
/usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': iconv will be deprecated in the future, use String#encode instead.
/usr/lib/ruby/vendor_ruby/puppet/provider/service/freebsd.rb:8: warning:class variable access from toplevel
/usr/lib/ruby/vendor_ruby/puppet/provider/service/freebsd.rb:9: warning: class variable access from toplevel
/usr/lib/ruby/vendor_ruby/puppet/provider/service/freebsd.rb:10: warning: class variable access from toplevel
/usr/lib/ruby/vendor_ruby/puppet/provider/service/bsd.rb:12: warning: class variable access from toplevel
Using help outputs:
# puppet help
/usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': iconv will be deprecated in the future, use String#encode instead.
Usage: puppet <subcommand> [options] <action> [options]
Available subcommands, from Puppet Faces:
ca Local Puppet Certificate Authority management.
catalog Compile, save, view, and convert catalogs.
certificate Provide access to the CA for certificate management.
certificate_request Manage certificate requests.
..
..
and so on.
These additional warnings are stderr messages as confirmed by redirecting
to 2>. Run time warnings in general are meant to be seen for developers not
users. This should be turned off for application code released to the world.
This is only seen on my server and not the laptop. The server runs the latest
ruby1.9.1 branch but the laptop still runs the ruby1.8 branch.
I have used aptitude safe-upgrade to keep both systems updated.
One difference between those systems and which may explain why the laptop did
not upgrade to ruby1.9.1. I purged ruby and puppet on the laptop during some
fault findings, some time ago. I then reinstalled puppet but not ruby.
I guess ruby1.8 was pulled in by a puppet dependency.
On the server, I did install ruby first (aptitude install ruby),
and then installed puppet (aptitude install puppet).
I wish, but maybe I'm not yet aware just how to do it, puppet would have
better control of which ruby version it use.
Cheers
Bertil
This is the server (puppet-agent).
==================================
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-2-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages puppet depends on:
ii dpkg 1.16.4.3
ii puppet-common 2.7.17-1
ii ruby 4.9
ii ruby1.8 [ruby-interpreter] 1.8.7.358-4
ii ruby1.9.1 [ruby-interpreter] 1.9.3.194-1
Versions of packages puppet recommends:
ii ruby [rdoc] 4.9
Versions of packages puppet suggests:
pn etckeeper <none>
pn puppet-el <none>
pn vim-puppet <none>
-- no debconf information
More versions from dpkg -l:
---------------------------
un ruby-interpreter <none>
ii ruby-json 1.7.3-1
un ruby-selinux <none>
ii ruby-shadow 2.1.4-2
un ruby-switch <none>
un ruby1.8-examples <none>
un ruby1.9.1-dev <none>
un ruby1.9.1-examples <none>
un rubygems1.9.1 <none>
This is the laptop acting as the puppet-server.
==============================================
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-2-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages puppet depends on:
ii dpkg 1.16.4.3
ii puppet-common 2.7.17-1
ii ruby1.8 [ruby-interpreter] 1.8.7.358-4
Versions of packages puppet recommends:
pn rdoc <none>
Versions:
---------
un ruby <none>
un ruby-interpreter <none>
ii ruby-json 1.7.3-1
un ruby-ldap <none>
un ruby-selinux <none>
ii ruby-shadow 2.1.4-2
un ruby-stomp <none>
un ruby-switch <none>
un ruby1.8-examples <none>
un ruby1.9.1-dev <none>
un ruby1.9.1-examples <none>
un rubygems1.9.1 <none>
ii puppet 2.7.17-1
ii puppet-common 2.7.17-1
ii puppetmaster-common 2.7.17-1
Reply to: