RHEL/Centos Server packages that conflict with mysql-libs should require a suitable replacement

Bug #1297822 reported by Jay Janssen
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Server moved to https://jira.percona.com/projects/PS
Invalid
Undecided
Unassigned
5.1
Invalid
Undecided
Unassigned
5.5
Invalid
Undecided
Unassigned
5.6
Invalid
Undecided
Unassigned
Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC
Status tracked in 5.6
5.5
Fix Released
Undecided
Unassigned
5.6
Fix Released
Undecided
Unassigned

Bug Description

On RHEL/CentOS server, if I try to install Percona Server on a system with mysql-libs, I get file conflicts. Why doesn't the Percona Server package require PS-5.1-shared or similar that will replace mysql-libs correctly?

This also applies to PXC.

Tags: pkg
tags: added: pkg
Revision history for this message
Valerii Kravchuk (valerii-kravchuk) wrote :

Can you, please, share some more details? Exact error messages during installation and exact Percona Server version(s) used at least.

Revision history for this message
Jay Janssen (jay-janssen) wrote :

Valerii: I mean these sorts of conflicts:

  file /usr/share/mysql/charsets/macce.xml from install of Percona-XtraDB-Cluster-server-56-1:5.6.15-25.5.759.rhel6.x86_64 conflicts with file from package mysql-libs-5.1.69-1.el6_4.x86_64
  file /usr/share/mysql/charsets/macroman.xml from install of Percona-XtraDB-Cluster-server-56-1:5.6.15-25.5.759.rhel6.x86_64 conflicts with file from package mysql-libs-5.1.69-1.el6_4.x86_64
  file /usr/share/mysql/charsets/swe7.xml from install of Percona-XtraDB-Cluster-server-56-1:5.6.15-25.5.759.rhel6.x86_64 conflicts with file from package mysql-libs-5.1.69-1.el6_4.x86_64

I must replace mysql-libs with Percona-Server-shared-51.x86_64 to be able to install 56 servers.

However, I noticed that the latest releases of Percona-Server-server-56 don't seem to have this problem. I presume if this packaging scheme is applied to PXC in the future as well, this bug may not be relevant any more since mysql-libs can stay where it is:

[root@localhost ~]# rpm -qa | grep -iE "percona|mysql"
Percona-Server-client-56-5.6.16-rel64.2.el6.x86_64
Percona-Server-server-56-5.6.16-rel64.2.el6.x86_64
mysql-libs-5.1.69-1.el6_4.x86_64
percona-release-0.0-1.x86_64
Percona-Server-shared-56-5.6.16-rel64.2.el6.x86_64

Revision history for this message
Valerii Kravchuk (valerii-kravchuk) wrote :

So, it seems to apply to PXC but NOT to latest Percona Server RPMs. I was also not able to find any conflict with 5.6.16-rel64.2 ones.

Revision history for this message
Raghavendra D Prabhu (raghavendra-prabhu) wrote :

> However, I noticed that the latest releases of Percona-Server-server-56 don't seem to have this problem.
> I presume if this packaging scheme is applied to PXC in the future as well, this bug may not be relevant any more since mysql-libs can stay where it is:

Yes, that is correct. This file-level conflict has been resolved
in -55 tree already.

Currently, it is required to remove mysql-libs prior to
installation of server to avoid this conflict.

Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-1658

Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3114

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.