PKG Library naming incompatibility between Percona-Server and Percona-XtraDB-Cluster RPMs
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona Server moved to https://jira.percona.com/projects/PS |
New
|
Undecided
|
Unassigned | ||
Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC |
New
|
Undecided
|
EvgeniyPatlan |
Bug Description
On CentOS, regular (non-Cluster) Percona 5.7 includes the package Percona-
These packages are marked as conflicting with one another, but provide non-overlapping shared libraries.
This seems to make it impossible to move from non-cluster Percona Server to cluster Percona Server without either doing something incredibly obnoxious like symlinking all of the shared libraries, or re-linking any software on the system which links against libmysqlclient.
My strong preference would be that Percona-
This incompatibility is present in the latest available packages, Percona-
This is similar to #1580764, but somewhat more critical since it affects what should be a safe operation of moving from Percona-Server to Percona-
I have literally no idea why this package is marked as Conflicts with `Percona-
tags: | added: pkg |
Changed in percona-xtradb-cluster: | |
assignee: | nobody → EvgeniyPatlan (evgeniy-patlan) |
summary: |
- Library naming incompatibility between Percona-Server and Percona- + PKG Library naming incompatibility between Percona-Server and Percona- XtraDB-Cluster RPMs |
Upstream made changes to the RPM scripts/ configuration in 5.7.14 to facilitate the install of multiple client library versions. Please include the changes in your release of 5.7.14.
https:/ /bugs.mysql. com/bug. php?id= 81384