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