Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at
Bug 1493659 - Use mariadb-connector-c-devel instead of mysql-devel or mariadb-devel
Summary: Use mariadb-connector-c-devel instead of mysql-devel or mariadb-devel
Alias: None
Product: Fedora
Classification: Fedora
Component: qt3
Version: rawhide
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Fedora Extras Quality Assurance
Depends On:
Blocks: 1486480
TreeView+ depends on / blocked
Reported: 2017-09-20 16:13 UTC by Michal Schorm
Modified: 2017-11-13 14:36 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2017-11-13 14:36:09 UTC
Type: Bug

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Qt Bug Tracker QTBUG-63108 0 None None None 2017-09-21 14:53:14 UTC

Description Michal Schorm 2017-09-20 16:13:27 UTC
Hello, please apply following command to the package SPECfile:

sed -i "s/mysql-devel/mariadb-connector-c-devel/" $(fedpkg gimmespec) ; \
sed -i "s/mariadb-devel/mariadb-connector-c-devel/" $(fedpkg gimmespec) ; \
sed -i "s/%{_libdir}\/mysql/%{_libdir}\/mariadb/" $(fedpkg gimmespec) ;

I've tested, that after the command ^ the package builds successfuly in KOJI and uses mariadb client library.

This change is currently applicable to the Rawhide (f28) only.

For more information check the tracking bugzilla.

Comment 1 Kevin Kofler 2017-09-21 14:53:15 UTC
Qt is not compatible with MariaDB Connector/C:

(This was filed against Qt 5 and 4, but probably applies to Qt 3 too.)

Comment 2 Kevin Kofler 2017-09-25 10:53:29 UTC
We probably need to backport:

Comment 3 Than Ngo 2017-11-13 14:36:09 UTC
backported the fix for qt3, it's now included in qt3-3.3.8b-72.fc28

Note You need to log in before you can comment on or make changes to this bug.