mythexport has a dependancy on the real mysql and does not install if MariaDB is being used

Bug #1603908 reported by Stephen Worthington on 2016-07-18
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
mythexport (Ubuntu)
Undecided
Unassigned

Bug Description

I am running a Ubuntu 16.04 PC with the MythTV packages installed on a test machine, prior to upgrading my Mythbuntu production PCs from Mythbuntu 14.04 to Mythbuntu 16.04. This is so that I can find any problems I will have with the upgrage process before I do it on the productions PCs. All my production MythTV boxes have a full set of mythtv packages installed, including the optional mythexport and mythimport packages.

Prior to installing MythTV on the test PC, I changed the default mysql install to MariaDB instead, due to needing readline in the mysql utility programs (Oracle has changed to using editline in the latest mysql versions). The normal MythTV backend and frontend package sets installed fine and work with MariaDB, but attempting to install the mythexport package (and mythimport also) results in apt telling me that it will uninstall MariaDB and install the real mysql packages. Looking at the dependencies for the mythexport and mythimport packages, they have a dependency for "mysql-client", whereas the mythtv-database package has a dependency for "mysql-client or virtual-mysql-client or mysql-client-5.7 or mysql-client-5.6". I do not believe that mythexport or mythimport actually need the real mysql and I am sure that they would work fine with MariaDB, so I would like to request that the mythexport and mythimport packages get this dependency problem fixed.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers