Your message dated Tue, 21 Oct 2025 07:30:02 +0000 (UTC)
with message-id <[email protected]>
and subject line innotop 1.11.4 available
has caused the Debian Bug report #660164,
regarding RFP: innotop -- monitor MySQL in real time
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.)


-- 
660164: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=660164
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: mysql-client-5.1
Version: 5.1.58-1
Severity: wishlist

Hi,

The embeded innotop seems to be currently at version 1.7.1.

Version 1.8.0 seems to be out for quite sometime now:

2010-11-06: version 1.8.0

   Changes:
   * Don't re-fetch SHOW VARIABLES every iteration; it's too slow on many hosts.
   * Add a filter to remove EVENT threads in SHOW PROCESSLIST (issue 32).
   * Add a timestamp to output in -n mode, when -t is specified (issue 37).
   * Add a new U mode, for Percona/MariaDB USER_STATISTICS (issue 39).
   * Add support for millisecond query time in Percona Server (issue 39).
   * Display a summary of queries executed in Query List mode (issue 26).

   Bugs fixed:
   * Made config-file reading more robust (issue 41).
   * Hostname parsing wasn't standards compliant (issue 30).
   * MKDEBUG didn't work on some Perl versions (issue 22).
   * Don't try to get InnoDB status if have_innodb != YES (issue 33).
   * Status text from the InnoDB plugin wasn't parsed correctly (issue 36).
   * Transaction ID from InnoDB plugin wasn't subtracted correctly (issue 38).
   * Switching modes and pressing ? for help caused a crash (issue 40).

2009-09-06: version 1.7.2

   Changes:
   * add support for --socket

   Bugs fixed:
   * remove cxn from $meta->{group_by} if there's only one connection displayed
   * fix for issue 19 - cxn column won't become visible when viewing two 
     connections after having viewed one connection
   * supress errors resulting from the addition of a 'BACKGROUND THREAD' 
     section in the output of 'show innodb status' 
   * possible fix for issue 22 - Useless use of a constant in void context
   * small change to set_to_tbl() around hiding the cxn column if there 
     aren't two or more connections

Please update to the last version

Cheers,

Laurent Bigonville

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_BE.utf8, LC_CTYPE=fr_BE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages mysql-client-5.1 depends on:
ii  debianutils        4.2.1
ii  libc6              2.13-26
ii  libdbd-mysql-perl  4.020-1+b1
ii  libdbi-perl        1.616-1+b2
ii  libgcc1            1:4.6.2-14
ii  libmysqlclient16   5.1.58-1
ii  libncurses5        5.9-4
ii  libreadline6       6.2-8
ii  libstdc++6         4.6.2-14
ii  libwrap0           7.6.q-22
ii  mysql-common       5.1.58-1
ii  perl               5.14.2-7
ii  zlib1g             1:1.2.6.dfsg-1

mysql-client-5.1 recommends no packages.

Versions of packages mysql-client-5.1 suggests:
pn  libterm-readkey-perl  <none>

-- no debconf information



--- End Message ---
--- Begin Message ---

Nowadays innotop is available in package mariadb-client only. Its version is 1.11.4, so I think this bug can be closed.

Thanks!
  Thorsten

--- End Message ---

Reply via email to