Bug 1148538
| Summary: | community-mysql has file conflicts with mariadb-server | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Daniel Berrangé <berrange> |
| Component: | community-mysql | Assignee: | Honza Horak <hhorak> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 21 | CC: | akozumpl, hhorak, jsilhan, jstanek, packaging-team-maint, pnemade, rholy, tim.lauridsen |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | mariadb-10.0.14-6.fc21 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-11-01 16:50:21 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: | |||
| Bug Depends On: | 1149160 | ||
| Bug Blocks: | |||
|
Description
Daniel Berrangé
2014-10-01 16:36:26 UTC
There seems to be something different going on with the virtual provides and choice between multiple options. Both 'community-mysql-server' and 'mariadb-server' provide 'mysql-server'. When asking to install 'mysql-server', yum will prefer 'mariadb-server' but dnf is preferring 'community-mysql-server'. Thanks for the report. mariadb-server package requires mysql-compat-client. Both mariadb and community-mysql provides mysql-compat-client. Solver chooses the package that contains the same files as the package that required it. This deserves deeper look why solver doesn't see file conflicts. Files data are not contained in repository metadata so solver cannot know about file conflicts. This is packaging bug of community-mysql. This doesn't really answer the question about why 'dnf install mysql-server' chooses community-mysql-server while 'yum install mysql-server' chooses mariadb-server. File conflicts doesn't come into that part of the decision, so this still seems a bug in dnf, becuase it has different behaviour to yum, not a bug in the packaging. DNF/libsolv simply uses different heuristics than YUM. I believe that if there are two packages providing the same thing, nobody can assume that his package will be preferred unless the preference is specified somehow. Well, the conflicts between community-mysql and mariadb are expected, even though it should be possible to have client from community-mysql and server from mariadb -- this should be hopefully fixed by including msql2mysql man page in correct page. Anyway, I've reported a bug for libsolv (BZ #1149160m not sure if it is correct component, but as I was told dnf or hawkey should not care about solving dependencies) that dnf behaves differently than yum (an generally incorrectly), even less rationally than yum (btw. yum describe the logic in [1], dnf does not document it at all, so we can definitely change it). But, to be honest, I would like to see some better implementation than yum does it now, something very simple for cases where both provides satisfy all dependencies (i.e. if it is possible to install either of the provides and all dependencies are satisfied). I described it in the bug mentioned above like "the provide with greater NEVRA is chosen". With that simple rule we could prioritize the default provide by defining higher epoch. Nothing complicated and it would allow us to prioritize mariadb over community-mysql very well. [1] http://yum.baseurl.org/wiki/CompareProviders mariadb-10.0.14-6.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/mariadb-10.0.14-6.fc21 Package mariadb-10.0.14-6.fc21: * should fix your issue, * was pushed to the Fedora 21 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing mariadb-10.0.14-6.fc21' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-12832/mariadb-10.0.14-6.fc21 then log in and leave karma (feedback). mariadb-10.0.14-6.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report. |