Bug 913529
| Summary: | mariadb : Conflicts with mytop | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Michael Schwendt <bugs.michael> |
| Component: | mariadb | Assignee: | Honza Horak <hhorak> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 19 | CC: | byte, hhorak, tgl |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | mariadb-5.5.31-1.fc19 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-06-06 02:23:28 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
The current state is that MariaDB took mytop and did some enhancements/fixes to the code, while mytop upstream seems dead to me for some time. I've contacted both (mytop maintainer and upstream) to confirm the above. Only if someone would pick changes made by MariaDB and start maintaining mytop again, we could remove it from MariaDB, otherwise I'd proposed retiring mytop in F19. This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19 I just ran mytop that came out of mariadb, and the error is can't locate Term/ReadKey.pm This means MariaDB should also install perl-TermReadKey when it is installed. That means a requires on perl-TermReadKey on mariadb Especially if we're dropping mytop (currently still conflicts when yum tries to process the transaction) We'll remove mytop from MariaDB, since MariaDB upstream is going to merge their changes to mytop upstream. Thus, removed from mariadb package in Fedora. mariadb-5.5.31-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/mariadb-5.5.31-1.fc19 Package mariadb-5.5.31-1.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing mariadb-5.5.31-1.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-9377/mariadb-5.5.31-1.fc19 then log in and leave karma (feedback). mariadb-5.5.31-1.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report. |
=> mytop-1.7-7.b737f60.fc19.src.rpm => mytop-1.7-7.b737f60.fc19.noarch in fedora-development-i386 File conflict with: mariadb-5.5.29-4.fc19.i686 /usr/bin/mytop [semi-automated bug report]