[DRE-maint] Bug#958973: ruby-curses: Emits warning: "rb_safe_level will be removed in Ruby 3.0", fixed upstream in 1.3.2

Axel Beckert abe at debian.org
Mon Apr 27 14:15:36 BST 2020


Package: ruby-curses
Version: 1.2.4-1+b3
Severity: important
Tags: fixed-upstream
Control: affects -1 irqtop

Hi,

running ruby-written irqtop on Debian Unstable contantly emits this
warning:

/usr/bin/irqtop:545: warning: rb_safe_level will be removed in Ruby 3.0

which makes it quite unusable as the curses screen looks like this after
a few seconds:


                                9                                          /usr/bin/irqtop:598: warning: rb_safe_level will be removed in Ruby 3.0
               2.4   11.6   12.2   15    /usr/bin/irqtop:613: warning: rb_safe_level will be removed in Ruby 3.0
       /usr/bin1.2    1.0    1.2ing: r6_safe_level will be removed in Ruby 3.0
               325    410    295    440                                       /usr/bin/irqtop:613: warning: rb_safe_level will b44removed in Ruby 3.0
                34                          /usr/bin/irqtop:598: warning: rb_safe_level will be removed in Ruby 3.0                           83
          /usr/bin/irqtop:613:18arning: rb_safe_level will be removed in Ruby 3.0
                                                                                 /usr/bin/irqtop:598: warning: rb_safe_l232    246    198ved in5Ruby 3.0
                 6      1     14      9        /usr/bin/irqtop:613: warning: rb_safe_level will be removed in Ruby 3.0   19     27     30     12
             /us22     32     33     29ng: rb_safe_level will be removed in Ruby 3.0
                18      3      6      4                                             /usr/bin/irqtop:613: warning: rb_safe_level will be removed in Ruby 3.0
                 0      3      0    184           /usr/bin/irqtop:598: warning: rb_safe_level will be removed in Ruby 3.0 6      2
                /usr/bin/irqtop:620: warning: rb_safe_level will be removed in Ruby 3.0

This has been fixed upstream in the 1.3.2 release, released in December
2019:

https://github.com/ruby/curses/commit/a9b9db9b5d5a4b52e3d0e0eaf0fbb2be839a3c29
https://github.com/ruby/curses/releases/tag/v1.3.2

So please upgrade ruby-curses in Debian Unstable to 1.3.2.

The current version in unstable, 1.2.4 is from September 2017 and there
were 6 new upstream releases since then.

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (600, 'testing'), (500, 'unstable-debug'), (500, 'buildd-unstable'), (110, 'experimental'), (1, 'experimental-debug'), (1, 'buildd-experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.5.0-1-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND, TAINT_UNSIGNED_MODULE
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages ruby-curses depends on:
ii  libc6         2.30-4
ii  libncursesw6  6.2-1
ii  libruby2.7    2.7.0-6
ii  libtinfo6     6.2-1
ii  ruby          1:2.7+1

ruby-curses recommends no packages.

ruby-curses suggests no packages.

-- no debconf information



More information about the Pkg-ruby-extras-maintainers mailing list