Hello, a MariaDB went through big changes and your package will probabbly need a patch. However your package FTBFS for a long time, 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. For more information check the tracking bugzilla.
Hi, Watching and waiting for a fix for this problem. Thanks, George... Problem 1: cannot install both mariadb-connector-c-3.0.2-20.fc28.x86_64 and mariadb-connector-c-3.0.2-19.fc28.x86_64 - package cherokee-1.2.104-1.fc25.x86_64 requires libmysqlclient.so.18()(64bit), but none of the providers can be installed - cannot install the best update candidate for package mariadb-connector-c-3.0.2-19.fc28.x86_64 - cannot install the best update candidate for package cherokee-1.2.104-1.fc25.x86_64 Problem 2: problem with installed package cherokee-1.2.104-1.fc25.x86_64 - package cherokee-1.2.104-1.fc25.x86_64 requires libmysqlclient.so.18()(64bit), but none of the providers can be installed - cannot install both mariadb-connector-c-3.0.2-20.fc28.x86_64 and mariadb-connector-c-3.0.2-19.fc28.x86_64 - mariadb-connector-c-3.0.2-20.fc28.i686 has inferior architecture - package mariadb-connector-c-devel-3.0.2-20.fc28.x86_64 requires mariadb-connector-c = 3.0.2-20.fc28, but none of the providers can be installed - cannot install the best update candidate for package mariadb-connector-c-devel-3.0.2-19.fc28.x86_64
Hello, MariaDB renamed its library to "libmariadb.so". MariaDB package has "Provides:" of the libmysqlclient.so, however it did not ship it. That was fixed by the false Provide removal. Basically, there are 2 options. Either use "commnity-mysql" package which provides desired library, or try to discuss with upstream move to MariaDB or atleast compatibility with both databases. Any of those ^ solutions are sufficent to solve this bug report, however, I'd prefer moving the project to MariaDB :)
cherokee-1.2.104-6.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2018-a6d868bcdc
cherokee-1.2.104-6.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-2394655c7f
cherokee-1.2.104-6.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-2394655c7f
cherokee-1.2.104-6.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-a6d868bcdc
cherokee-1.2.104-6.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.
cherokee-1.2.104-6.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.