libmysqlclient20 dependency issue
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mysql-5.7 (Ubuntu) |
Triaged
|
Low
|
Unassigned | ||
Xenial |
Triaged
|
Low
|
Unassigned |
Bug Description
On Ubuntu 16.04 LTS (xenial), I've found that libmysqlclient20 depends on mysql-common (>= 5.5)
apt-cache show libmysqlclient20 | grep Depends
Depends: mysql-common (>= 5.5), libc6 (>= 2.14), libgcc1 (>= 1:3.0), libstdc++6 (>= 4.1.1), zlib1g (>= 1:1.1.4)
Can you please change this to simply "mysql-common" instead of the versioned one?
As this now makes impossible for example to install the Codership Galera packages from ( deb http://
Now I get this:
root@node1:~# apt-get install mysql-wsrep-5.6 libdbd-mysql-perl
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
libdbd-mysql-perl : Depends: libmysqlclient20 (>= 5.7.11) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
PS: Btw I've filed an issue to Codership too, maybe there is a way to solve this there:
https:/
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: libmysqlclient20 5.7.15-
ProcVersionSign
Uname: Linux 4.4.0-38-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: GNOME-Flashback
Date: Tue Oct 18 13:09:03 2016
KernLog:
Logs.var.
MySQLConf.
MySQLConf.
[mysqldump]
quick
quote-names
max_allowed_packet = 16M
MySQLConf.
[mysqld_safe]
syslog
MySQLVarLibDirL
SourcePackage: mysql-5.7
UpgradeStatus: No upgrade log present (probably fresh install)
modified.
modified.
mtime.conffile.
mtime.conffile.
Thank you for your report.
We don't treat an issue affecting third party repositories as bugs in Ubuntu. But in this case the versioned dependency can be dropped anyway, so we can do that for you at least in the development release. So I'll leave this open but with Importance: Low.
I'm not sure if this qualifies for an update in Xenial. See https:/ /wiki.ubuntu. com/StableRelea seUpdates for our policies, rationale and procedure. Perhaps we could bundle it in other updates though, if others agree that it is a no-op with no regression risk. So I'll create a task for Xenial and leave it open.
There are two "proper" solutions for Ubuntu. One is to package it in the distribution the traditional way so that it is properly integrated. The other is for Codership to ship a snap, which untangles what they want to ship as an external third party with what the distribution ships.