Your message dated Thu, 5 Jul 2012 19:23:45 -0600
with message-id <[email protected]>
and subject line Re: Bug#680420: deprecation warning: iconv
has caused the Debian Bug report #680420,
regarding deprecation warning: iconv
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
680420: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680420
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: apt-listbugs
Version: 0.1.7
Severity: normal
Since a few weeks (IIRC), apt-listbugs barfs at each invocation a deprecation
warning about iconv (as a Ruby lib, presumably), e.g.:
Retrieving bug reports... Done
Parsing Found/Fixed information... Done
/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
Reading changelogs... Done
I guess that's due to the recent ruby 1.9 migration [1], but I haven't verified
the details. It would be nice if these warnings could be silenced, ideally by
moving away from the deprecated functionalities :)
Thanks for maintaining apt-listbugs,
Cheers.
[1] https://lists.debian.org/debian-devel-announce/2012/06/msg00001.html
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.2.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages apt-listbugs depends on:
ii apt 0.9.7.1
ii libgettext-ruby1.8 2.2.1-2
ii libruby1.8 [libzlib-ruby1.8] 1.8.7.358-4
ii ruby-debian 0.3.8+b1
ii ruby-gettext [libgettext-ruby1.8] 2.2.1-2
ii ruby-httpclient 2.2.4-1
ii ruby-xmlparser 0.7.2-2
ii ruby1.8 1.8.7.358-4
apt-listbugs recommends no packages.
Versions of packages apt-listbugs suggests:
ii chromium [www-browser] 20.0.1132.41~r143299-1
ii debianutils 4.3.2
ii epiphany-browser [www-browser] 3.4.2-1
ii iceweasel [www-browser] 10.0.5esr-2
ii reportbug 6.4
ii w3m [www-browser] 0.5.3-8
-- no debconf information
--- End Message ---
--- Begin Message ---
On Thu, Jul 05, 2012 at 10:52:02PM +0200, Francesco Poli wrote:
> This is really awkward: I have never seen such warnings on any of the
> Debian boxes I use, not even in my sid chroot (I've just checked).
Argh, shame on me! It was actually another custom APT hook of mine that
calls into puppet and apparently trigger that warning. As it was ruby, I
immediately thought of apt-listbugs, while the culprit was something
else.
Closing the bug now.
Sorry for the noise.
--
Stefano Zacchiroli zack@{upsilon.cc,pps.jussieu.fr,debian.org} . o .
Maître de conférences ...... http://upsilon.cc/zack ...... . . o
Debian Project Leader ....... @zack on identi.ca ....... o o o
« the first rule of tautology club is the first rule of tautology club »
signature.asc
Description: Digital signature
--- End Message ---
