FS#61457 - [percona-server] conflict with mariadb-libs
Attached to Project:
Community Packages
Opened by Michael Taboada (lilmike) - Friday, 18 January 2019, 15:40 GMT
Last edited by Massimiliano Torromeo (mtorromeo) - Friday, 18 January 2019, 22:12 GMT
Opened by Michael Taboada (lilmike) - Friday, 18 January 2019, 15:40 GMT
Last edited by Massimiliano Torromeo (mtorromeo) - Friday, 18 January 2019, 22:12 GMT
|
Details
Description:
error: failed to commit transaction (conflicting files) mariadb-libs: /usr/lib/mysql/plugin/dialog.so exists in filesystem (owned by percona-server) Additional info: * package version(s) mariadb-libs 10.3.12-2 percona-server 8.0.13_3-3 Steps to reproduce: Upgrade libmariadbclient to mariadb-libs with percona-server installed. |
This task depends upon
Closed by Massimiliano Torromeo (mtorromeo)
Friday, 18 January 2019, 22:12 GMT
Reason for closing: Fixed
Additional comments about closing: percona-server-8.0.13_3-5
Friday, 18 January 2019, 22:12 GMT
Reason for closing: Fixed
Additional comments about closing: percona-server-8.0.13_3-5
The conflicting plugin(s) got moved from mariadb 10.1.37-1 to mariadb-libs 10.3.12-2 during the recent update. They were *not* previously in libmariadbclient as per the filelist. So historically this worked, and either the package needs to go back to the old way of splitting up the files, or packages which formerly conflicted mariadb alone, now need to conflict mariadb-libs.
Perhaps we should just move them to mariadb-libs to mariadb package...
The percona upstream (and I guess also the previous mariadb build process) distributes it as part of the "server" package even though it's part of the client authentication process.
Logically I wouldn't mind moving that plugin in the libperconaserver package similarly to mariadb but the only way to make it not conflict is moving everything from /usr/lib/mysql to /usr/lib/perconaserver which is probably not that bad.