Bug 1643734
Summary: | fpc compiled programs that use mysql break when built/run with mariadb due to client lib name missmatch | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Jim Lieb <lieb> |
Component: | fpc | Assignee: | Joost van der Sluis <joost> |
Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 28 | CC: | joost, mattia.verga |
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: | 2019-05-28 23:03:08 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
Jim Lieb
2018-10-28 03:24:26 UTC
I think the problem is that libmysqlclient is provided by mariaDB in its mariadb-connector-c-devel package and not in mariadb-connector-c: $ dnf repoquery -l mariadb-connector-c-devel | grep libmysqlclient /usr/lib/libmysqlclient.so /usr/lib/libmysqlclient_r.so /usr/lib64/libmysqlclient.so /usr/lib64/libmysqlclient_r.so /usr/lib64/libmysqlclient.so /usr/lib64/libmysqlclient_r.so /usr/lib/libmysqlclient.so /usr/lib/libmysqlclient_r.so $ dnf repoquery -l mariadb-connector-c | grep libmysqlclient <EMPTY RESPONSE> while community-mysql-libs provides it in its runtime package and not in devel: $ dnf repoquery -l community-mysql-libs | grep libmysqlclient /usr/lib/mysql/libmysqlclient.so.20 /usr/lib/mysql/libmysqlclient.so.20.3.8 /usr/lib/mysql/libmysqlclient.so.20 /usr/lib/mysql/libmysqlclient.so.20.3.10 /usr/lib64/mysql/libmysqlclient.so.20 /usr/lib64/mysql/libmysqlclient.so.20.3.8 /usr/lib64/mysql/libmysqlclient.so.20 /usr/lib64/mysql/libmysqlclient.so.20.3.10 $ dnf repoquery -l community-mysql-libs-devel | grep libmysqlclient <EMPTY RESPONSE> Maybe cqr should require community-mysql-libs at runtime instead of mariadb-connector-c-devel? I'm unfamiliar with all of these packages mariadb<->mysql. Something has to give here. This is both a mix of mysql forks and bad packaging, in reverse image no less... If mariadb is the post-Larry E. future, it should conform to common package, package-devel practice and have the complete *.so mix in the package and the *.a and headers etc. in the -devel. And if mariadb is supposed to be a plug-and-play of "old" mysql, they shouldn't muck with the runtime footprint. Also, I see no reason to have a community-mysql unless there are unavoidable API legacy issues. I'm also unfamiliar with fpc and its ecosystem so I am unclear why this library must be dynamically loaded. But that is an upstream, not packaging issue. See BZ #1592176 for the related bug. This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |