Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
----------------------
Currently "mariadb-server" in rhel7 doesn't provide "mysql-server" which sometimes leads to weird behaviour if a third-party package has a "Require: mysql-server" line.
For example: https://kojipkgs.fedoraproject.org//work/tasks/6493/11886493/root.log
DEBUG util.py:393: Error: No Package found for mysql-server
DEBUG util.py:515: Child return code was: 1
Unlike f22, f23, rawhide which all have "mysql-server" provision and work with the same package just fine: https://kojipkgs.fedoraproject.org//work/tasks/6102/11886102/root.log
Details:
--------
The difference is that Fedora obsoletes & provides mysql-server, this is the expected behaviour:
%package server
...
%if %{with mysql_names}
Provides: mysql-server = %{sameevr}
Provides: mysql-server%{?_isa} = %{sameevr}
Provides: mysql-compat-server = %{sameevr}
Provides: mysql-compat-server%{?_isa} = %{sameevr}
%endif
%{?obsoleted_mysql_case_evr:Obsoletes: MySQL-server < %{obsoleted_mysql_case_evr}}
%{?with_conflicts:Conflicts: community-mysql-server}
%{?with_conflicts:Conflicts: mariadb-galera-server}
%{?obsoleted_mysql_evr:Obsoletes: mysql-server < %{obsoleted_mysql_evr}}
Spec in RHEL7 only obsoletes without provide:
%package server
...
Provides: mysql-compat-server = %{epoch}:%{version}-%{release}
Provides: mysql-compat-server%{?_isa} = %{epoch}:%{version}-%{release}
Obsoletes: mysql-server < %{obsoleted_mysql_evr}
Summary:
--------
Of course, it's possible to use "mysql-compat-server" in all cases and it will work. But I doubt that this difference between Fedora and RHEL branches in such popular package is the desired strategy.
(In reply to Denis Fateyev from comment #0)
> Of course, it's possible to use "mysql-compat-server" in all cases and it
> will work. But I doubt that this difference between Fedora and RHEL branches
> in such popular package is the desired strategy.
To be honest it was desired this way. We consulted this topic during RHEL-7 development and decided not to provide mysql-server for mariadb packages, because users must be clear what to use.
Now, with MariaDB 10.x less compatible with MySQL it seems to be the way also in Fedora (i.e. we should remove mysql-server provide for mariadb-server, since it's not 100% compatible any more and it was more meant to overcome transition period). I'm sorry for troubles.