Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Duplicate
-
10.2.11
-
None
-
Centos 7
Description
I get a repo conflict ip attempting to do a yum update
Transaction check error:
file /etc/my.cnf from install of MariaDB-common-10.2.11-1.el7.centos.x86_64 conflicts with file from package Percona-Server-shared-56-5.6.37-rel82.2.el7.x86_64
This is simple - and I can get around it - but not re-package and fix it
This issue has been around for a while - I ran into it upgrading from 10.1.28 to 10.2.9, and is also found on a Chinese site also
Oct 6, 2017 - Error: Percona-XtraDB-Cluster-shared-57 conflicts with Percona-Server-shared-56-5.6.37-rel82.2.el7.x86_64. Error: Percona-Server-devel-57 conflicts with Percona-Server-devel-55-5.5.57-rel38.9.el7.x86_64. Error: Package: 1:mariadb-server-5.5.56-2.el7.x86_64 (base). Requires: mariadb-libs(x86-64) ...
RELATING to the libs => http://www.cnblogs.com/lwf-blog/p/7631787.html and english version may come up using https://translate.google.com/translate?hl=en&sl=zh-CN&u=http://www.cnblogs.com/lwf-blog/p/7631787.html&prev=search
I went around this "libs" issue with an rpm --force command - but yum has no ability to "force" - even for an issue as simple as the my.cnf file. See https://dba.stackexchange.com/questions/186993/solution-oom-killer-was-killing-mariadb-every-hour-or-so
The my.cnf should not be "changed" and this should go in as an "rpmnew" file so someone - whoever packages these files needs to address this
Attachments
Issue Links
- duplicates
-
MDEV-9800 Conflicts upon installing MariaDB server over Percona server on CentOS and RHEL
-
- Open
-
- is duplicated by
-
MDEV-17722
MariaDB common update file fails
-
- Open
-
Activity
Generally, yum upgrade from other providers' packages to MariaDB's is not supported. It might work in some lucky cases, but usually it doesn't.
Particularly, issues upon upgrading from Percona are filed as MDEV-9800 .
It's inconvenience, but since it has a rather simple workaround – removing old packages and installing new ones – it hasn't been a task of highest priority.
OK - I see but - these are files FROM the Mariadb repo causing the conflict - not another vendor.
You are not seeing the issue - which is with the version of libs that conflict are those from mariadb-common which actually are requiring Percona server - which are really just two libs and the etc/my.cnf file
One has to go to http://yum.mariadb.org/10.2/centos7-amd64/rpms/MariaDB-10.2.11-centos7-x86_64-common.rpm and do an "rpm -Uvh [filename link] --force" to install that one conflicting file because of a "my.cnf" file conflict
Then one can yum upgrade the rest once the conflict is forced through and away
Mariadb-libs are obsoleted by Percona-Server-shared-56-5.6.37-rel82.2.el7.x86_64 which provides
/etc/my.cnf
/usr/lib64/libmysqlclient.so.18.1.0
/usr/lib64/libmysqlclient_r.so.18.1.0
See also https://bugs.launchpad.net/percona-server/+bug/1558435
The current mariadb-libs-5.5.56-2.el7 RPM for x86_64 - for CentOS 7.4.1708 for x86_64 / Packages which provides:
mariadb-libs
config(mariadb-libs)
libmysqlclient.so.18()(64bit)
libmysqlclient.so.18(libmysqlclient_16)(64bit)
libmysqlclient.so.18(libmysqlclient_18)(64bit)
mariadb-libs(x86-64)
mysql-libs
mysql-libs(x86-64)
comes up stating it is OBSELETED by Percona-server 56 - which in reality ARE the new libs - "mariadb-libs" - if one READS the Chinese site the issue is shown that happens when trying to upgrade to 10.2 and results in a forced result to the Percona-server 56 which are really just two lib files => SEE AGAIN https://translate.google.com/translate?hl=en&sl=zh-CN&u=http://www.cnblogs.com/lwf-blog/p/7631787.html&prev=search
So . . . this is NOT an "old package" to be removed - it is the current dependency issue of version 10.2.11 where the etc/cnf file in Percona-server conflicts with a maraidb-common etc/cnf replacement