[MDEV-10376] innotop is not working: missing dependency on libterm-readkey-perl Created: 2016-07-14  Updated: 2016-11-26  Resolved: 2016-11-26

Status: Closed
Project: MariaDB Server
Component/s: Packaging, Platform Debian
Affects Version/s: 10.1.14
Fix Version/s: N/A

Type: Bug Priority: Minor
Reporter: Steve Hall Assignee: Otto Kekäläinen
Resolution: Fixed Votes: 0
Labels: None
Environment:

Ubuntu 16.04


 Description   

In the same vein as https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/1000605
and extending MDEV-5625. Specifically see https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/1000605/comments/6 for reasoning.

innotop will not work on Ubuntu 16.04 without libterm-readkey-perl. It should be a dependency of the mariadb-client-10.1 rather than a suggestion. If libterm-readkey-perl can not or should not be a dependency of mariadb-client-10.1 then innotop should be broken out into a new package with the dependency on libterm-readkey-perl correctly defined.

Thanks!



 Comments   
Comment by Otto Kekäläinen [ 2016-11-26 ]

In MariaDB.org 10.2.3 and in MariaDB 10.0.x at Debian/Ubuntu we already have:

Recommends: libdbd-mysql-perl (>= 1.2202), libdbi-perl, libterm-readkey-perl

As Recommends is stronger than Suggests, these are already installed along the MariaDB client automatically:

# apt install mariadb-client-10.2
 
Reading package lists... Done
 
Building dependency tree       
Reading state information... Done
 
The following extra packages will be installed:
 
  libdbd-mysql-perl libdbi-perl libmariadb3 libmysqlclient18 libterm-readkey-perl mariadb-client-core-10.2 mariadb-common
 
Suggested packages:
 
  libclone-perl libmldbm-perl libnet-daemon-perl libsql-statement-perl
 
The following NEW packages will be installed:
 
  libdbd-mysql-perl libdbi-perl libmariadb3 libmysqlclient18 libterm-readkey-perl mariadb-client-10.2 mariadb-client-core-10.2 mariadb-common
 
0 upgraded, 8 newly installed, 0 to remove and 0 not upgraded.

Therefore I consider this issue solved.

Generated at Thu Feb 08 07:41:46 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.