Dne 26. 11. 24 v 15:00 Mamoru TASAKA via ruby-sig napsal(a):
Vít Ondruch via ruby-sig wrote on 2024/11/26 17:35:Hi everybody.Yet another update of Ruby 3.4, this time to 4d8c793bc3 and the build is here:https://koji.fedoraproject.org/koji/taskinfo?taskID=126242984Nothing really outstanding. The only change worth noting that the RDoc issue mentioned earlier by Mamoru was fixed.Please give it try and as always, please let me know your findings.BTW it seems that were are not less then 50 packages which needs to get fixed for Ruby 3.4 and from those 13 have been FTBFS already. So thanks everybody for helping.VítHello Vít, and ruby-sig folks: I think (not sure most but at least) many of the failures are due to ruby 3.4 Hash#inspect formatting change: for those failures maybe we can just patch out them as a last resort.
These are unfortunate, but as long as we can build all arch dependent packages, we might consider them non-blocking. These are typically only test suite problems, so we can fix those later. Of course with Ruby 3.4 release, there is change these will be fixed by communities (while old RoR we have in Fedora ATM blocks updates of some packages, such as Rack 🤷).
Currently the failures I feel difficult to fix are: * rubygem-websocket https://copr.fedorainfracloud.org/coprs/vondruch/mpb/build/8312136/ Due to https://bugs.ruby-lang.org/issues/20265 change,NEWOBJ macro is removed, then currently rubygem-websocket really fails to compile.For now I have no idea how to replace this macro.
I can see just the `base64` issue. Does the NEWOBJ thing pops up once the `base64` issue is fixed?
* rubygem-mysql2
I have disabled the offending test cases today, because this blocks rubygem-railties. The issue is tracked here:
https://bugzilla.redhat.com/show_bug.cgi?id=2323148 and I have also opened upstream ticket today: https://github.com/brianmario/mysql2/issues/1382Overall, the failures such as `#<Mysql2::Error::ConnectionError: TLS/SSL error: unexpected eof while reading>` reminds me this rubygem-pg issue a bit:
https://src.fedoraproject.org/rpms/rubygem-pg/c/73df744331e064436ef3e6503f667c957731150f But I might be completely wrong.
* rubygem-clockwork
I hope this will get removed prior it gets problematic. Ignoring this one for the time being.
https://lists.fedoraproject.org/archives/list/de...@lists.fedoraproject.org/thread/ICMJ7ROZCQRCPM6X7JIXF7YVTSXNMB2A/ Vít
These 2 packages hang up at %check , rpmbuild cannot finish currently.I guess Timeout.#timeout behavior somewhat changed, but don't know currentlyhow to fix. Regards, Mamoru
OpenPGP_signature.asc
Description: OpenPGP digital signature
-- _______________________________________________ ruby-sig mailing list -- ruby-sig@lists.fedoraproject.org To unsubscribe send an email to ruby-sig-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/ruby-sig@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
