[MDEV-14548] rpm file conflict Created: 2017-11-30 Updated: 2020-04-21 Resolved: 2017-11-30 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Configuration, Packaging |
| Affects Version/s: | 10.2.11 |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Major |
| Reporter: | Wilbur Union | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Environment: |
Centos 7 |
||
| Issue Links: |
|
||||||||||||
| Description |
|
I get a repo conflict ip attempting to do a yum update Transaction check error: 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 |
| Comments |
| Comment by Elena Stepanova [ 2017-11-30 ] |
|
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. |
| Comment by Wilbur Union [ 2017-11-30 ] |
|
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 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 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 |