MDEV-38771 RPM conflicts between MariaDB-common and mysql-common #4639
+0
−4
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mysql-common and MariaDB-common don't install the same files. mysql-common (in MySQL 8.0) installs character set files (/usr/share/mysql/charsets/*) and /usr/lib64/mysql (directory only). MariaDB common installs character set files in /usr/share/mariadb and the same /usr/lib64/mysql directory along with client plugins in /usr/lib64/mysql/plugin. The RPM rules of conflict only will cause troubles on directories if they are installed with different metatadata (selinux, ownership, permissions) which isn't the case. As the character sets are at a different location MariaDB-common isn't obsoleting mysql-common in a way that provides compatibilty with mysql-common, for mysql-libs or otherwise, so its just creating an install conflict. Users installing perl-DBD-MySQL notice this because its mysql-libs dependency pulls mysql-common, which conflicts with MariaDB-common. We correct by removing the conflict and the provides of MariaDB-common with resepect to mysql-common.
grooverdan
added
the
MariaDB Foundation
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
mysql-common and MariaDB-common don't install the same files. mysql-common (in MySQL 8.0) installs character set files (/usr/share/mysql/charsets/*) and /usr/lib64/mysql (directory only).
MariaDB common installs character set files in /usr/share/mariadb and the same /usr/lib64/mysql directory along with client plugins in /usr/lib64/mysql/plugin. The RPM rules of conflict only will cause troubles on directories if they are installed with different metatadata (selinux, ownership, permissions) which isn't the case.
As the character sets are at a different location MariaDB-common isn't obsoleting mysql-common in a way that provides compatibilty with mysql-common, for mysql-libs or otherwise, so its just creating an install conflict.
Users installing perl-DBD-MySQL notice this because its mysql-libs dependency pulls mysql-common, which conflicts with MariaDB-common.
We correct by removing the conflict and the provides of MariaDB-common with resepect to mysql-common.