Bug 1494085

Summary: Use mariadb-connector-c-devel instead of mysql-devel or mariadb-devel
Product: [Fedora] Fedora Reporter: Michal Schorm <mschorm>
Component: qtAssignee: Than Ngo <than>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: itamar, jreznik, kasal, kevin, me, rdieter, smparrish, than
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: 2017-10-23 19:16:45 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:    
Bug Blocks: 1486480    

Description Michal Schorm 2017-09-21 12:44:24 UTC
Hello, a MariaDB went through big changes and your package will probabbly need a patch. However your package FTBFS in rawhide, so I have no way to test the patch.

In most cases, this command was enough to fix all the issues:

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) ; \
sed -i "s/mariadb-connector-c-devel/mariadb-connector-c-devel openssl-devel/" $(fedpkg gimmespec) ;

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



FTBFS problem:
package compat-openssl10-devel-1:1.0.2j-9.fc28.x86_64 conflicts with openssl-devel provided by openssl-devel-1:1.1.0f-9.fc27.x86_64



For more information check the tracking bugzilla.

Comment 1 Kevin Kofler 2017-09-21 14:53:39 UTC
Qt is not compatible with MariaDB Connector/C:
https://bugreports.qt.io/browse/QTBUG-63108

Comment 2 Rex Dieter 2017-09-21 14:55:41 UTC
Furhter, qt(4) cannot use openssl-1.1.x (or newer) either.  compat-openssl10 is required here.  Did mariadb packaging change to hard-code openssl-devel again?  If so, please reconsider and revert to allow either openssl headers if possible.

Comment 3 Kevin Kofler 2017-09-25 10:53:32 UTC
For QTBUG-63108, we probably need to backport:
https://codereview.qt-project.org/#/c/205874/

Comment 4 Michal Schorm 2017-10-23 14:34:10 UTC
Rex:

MariaDB updated to OpenSSL 1.1 in 10.2 version. In Fedora, that update is backported even to mariadb 10.1 (f26, f25).

mariadb-connector-c builds with openssl 1.1, however it does not require it, so there should not be a RPM conflict.
However your question is - I think - wherther it would work properly with openssl 1.0 too, when build with openssl 1.1.
There, I'm not sure. I would need to ask the upstream, but it is IMHO bad idea in general (to use it like that).



Rex, Kevin:

However if QT does not need OpenSSL with MariaDB, but it only use it in different part, we should not encounter this issue anayway.

Comment 5 Rex Dieter 2017-10-23 19:16:45 UTC
Thanks, my only concern was the openssl conflicts referenced in the initial comment.  Seems like things are ok now.


%changelog
* Mon Oct 23 2017 Rex Dieter <rdieter> - 1:4.8.7-32
- BR: mariadb-connector-c-devel (f28+, #1494085)
- backport mysql driver mariadb fix (QTBUG-63108)

Comment 6 Michal Schorm 2017-10-23 19:41:28 UTC
I'm pleased to hear that :)