Hello, Please note that this comment was generated automatically. If you feel that this output has mistakes, please contact me via email (mhroncok). Your package (rubygem-mysql2) Fails To Install in Fedora 34: can't install rubygem-mysql2: - nothing provides libruby.so.2.7()(64bit) needed by rubygem-mysql2-0.5.3-5.fc33.x86_64 If you know about this problem and are planning on fixing it, please acknowledge so by setting the bug status to ASSIGNED. If you don't have time to maintain this package, consider orphaning it, so maintainers of dependent packages realize the problem. If you don't react accordingly to the policy for FTBFS/FTI bugs (https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/), your package may be orphaned in 8+ weeks. P.S. The data was generated solely from koji buildroot, so it might be newer than the latest compose or the content on mirrors. P.P.S. If this bug has been reported in the middle of upgrading multiple dependent packages, please consider using side tags: https://docs.fedoraproject.org/en-US/rawhide-gating/multi-builds/ Thanks!
Hello, This is the first reminder (step 3 from https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/#_package_removal_for_long_standing_ftbfs_and_fti_bugs). If you know about this problem and are planning on fixing it, please acknowledge so by setting the bug status to ASSIGNED. If you don't have time to maintain this package, consider orphaning it, so maintainers of dependent packages realize the problem.
I will take it. The situation is there are test failures that may come from gcc-11 or new mariadb version used as a build dependency packages on rawhide. This does not happen on f33. https://github.com/brianmario/mysql2/issues/1152 My plan is 1. Recover the upstream CI at first. Because right now the upstream CI is dead. https://github.com/brianmario/mysql2/pull/1154 2. Fix the test failures providing the reproducing script to the upstream.
So: * I built mariadb 10.5.8 on F-33 and rubygem-mysql2 0.5.3 test suite FAILs. https://copr.fedorainfracloud.org/coprs/mtasaka/mariadb-new-test/builds/ * I downgraded mariadb to 10.4.17 (using epoch on copr) and rubygem-mysql2 0.5.3 test suite PASSes https://copr.fedorainfracloud.org/coprs/mtasaka/mariadb-old-rawhide-test/builds/ So, my brief guess is that this is related to mariadb change: 10.4.17 -> 10.5.8, and not related to ruby or gcc changes.
Note: > I downgraded mariadb to 10.4.17 (using epoch on copr) and rubygem-mysql2 0.5.3 test suite PASSes I downgraded mariadb to 10.4.17 (using epoch on copr) *on rawhide* and rubygem-mysql2 0.5.3 test suite PASSes
Thanks for your investigation. It's quite useful!
This bug appears to have been reported against 'rawhide' during the Fedora 34 development cycle. Changing version to 34.
FEDORA-2021-590938086b has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2021-9c6e11fac7 has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.
Vit, thanks for your working to build the package on the following commit! https://src.fedoraproject.org/rpms/rubygem-mysql2/c/6d35cbef77794eaacac9176958e50005d2daddbb?branch=main
I opened the issue ticket on mariadb here. https://bugzilla.redhat.com/show_bug.cgi?id=1929713