Bug 2036572

Summary: mariadb-server dependency pulls in community-mysql for the client
Product: [Fedora] Fedora Reporter: Honza Horak <hhorak>
Component: mariadbAssignee: Michal Schorm <mschorm>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 34CC: damien.ciabrini, hhorak, ljavorsk, mbayer, mkocka, mmuzila, mschorm, SpikeFedora
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-01-03 11:18:31 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Honza Horak 2022-01-03 09:01:54 UTC 
Problem description:

In some circumstances, installing mariadb-server pulls in community-mysql package.

It's not showing the same results for me when running it in an empty container, so it likely depends on other components installed.

It's reported more in detail on upstream mailing list:
https://lists.launchpad.net/maria-discuss/msg06179.html

The discussion there leads to make the requirements from *-server to client package more explicit.

There has been some efforts to make the combination of mariab-server and community-mysql (client tools) working, but I'm not entirely sure about usefulness of this.

At least for the Fedora packaging, there are more ways how packages can say that they do not care about which mysql client tools are available:

1) Requires: (mysql or mariadb)
2) Requires: mysql-compat-client
3) Requires: /usr/bin/mysql

So, maybe we can change the requirement to be more explicit and then fix potential "conflicts" issues by changing the requirements to one of the options above (likely the (1) or (2) option).
Comment 1 Honza Horak 2022-01-03 11:18:31 UTC 
There is actually bz#2026933 already, so closing this one as a duplicate.

*** This bug has been marked as a duplicate of bug 2026933 ***