PT-2538 - fix compatible issues with DBD::MariaDB - #1128
Open
oblitorum wants to merge 1 commit into
Open
Conversation
oblitorum
force-pushed
the
PT-2538_fix_compatible_issues_with_DBD_MariaDB
branch
from
June 6, 2026 10:52
6cbb086 to
99a442f
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Sometimes, DBD::MariaDB is more appreciated than DBD::mysql. For example, on a RHEL system, if you setup and install the MariaDB server from official MariaDB mariadb_repo_setup tool, and then you try to install the percona-toolkit package, you’re likely to encounter into an error similar to this:
Because percona-toolkit depends on DBD::mysql, which resolved as perl-DBD-MySQL package on rpm system, which then depends on the mysql-common package. And the mysql-common package is conflict with the MariaDB-common package from the official MariaDB repo. In this case, DBD::MariaDB is preferred for avoiding such conflicts.
In current percona-toolkit (3.7.x), DBD::MariaDB is not regarded at many places, this patch adds the regard and makes an adjustment to the rpm/deb packaging so that
perl(DBD::MariaDB)could be a replacement toperl(DBD::mysql), as a dependency.