Dne 03. 01. 25 v 15:35 Mamoru TASAKA via ruby-sig napsal(a):
Vít Ondruch via ruby-sig wrote on 2025/01/03 23:24:

Dne 03. 01. 25 v 10:29 Mamoru TASAKA via ruby-sig napsal(a):
Vít Ondruch via ruby-sig wrote on 2025/01/03 6:07:
Happy new year to everybody,

During the Christmas break, upstream indeed release Ruby 3.4.0 and actually also Ruby 3.4.1. As always, I am back with the updated packages. The scratch build succeeded here:

https://koji.fedoraproject.org/koji/taskinfo?taskID=127496631

The changes are in my PR and the mini mass rebuild is churning here:

https://copr.fedorainfracloud.org/coprs/vondruch/mpb.32

Nothing really notable happened, except the RDoc documentation issue reported in this thread earlier.

My next steps will be to check if I am able to drop the release back to 1, squash the commits and we should follow with mass rebuild. However, the change proposal was not approved yet. I'd like to finish our mass rebuild prior the Fedora mass rebuild, but we will see. There are a few outstanding FTBFS packages, but there should not be any showstopper.

As always please give the Ruby 3.4.1 try and any feedback will be appreciated.


Cheers


Vít


Looks like now (after a very small window) now the srpm you provided
began to FTBFS:
https://koji.fedoraproject.org/koji/taskinfo?taskID=127506468

Most likely this is due to openssl change:
openssl-3.2.2-8.fc42 -> openssl-3.2.2-10.fc42

-9 only adds plans/pq-container.fmf (so I don't think this affects koji build)
so most likely due to -10 change:
https://src.fedoraproject.org/rpms/openssl/c/3e4eea28e54d0550f621d087a90b82d7a4b57883?branch=rawhide

Regards,
Mamoru


Reported here:


https://bugzilla.redhat.com/show_bug.cgi?id=2335414

Vít


Now looking at this, the above test failure seems to be happening at the very first
stage of openssl initialization with OPENSSL_FORCE_FIPS_MODE is enabled:

So in ruby.src.rpm Source15 test_openssl_fips.rb : this sets
ENV['OPENSSL_FORCE_FIPS_MODE'] = '1', then the above test seems to be failing just after

"require 'openssl'" and error message suggests OPENSSL_init_ssl is failing.


I've noted the very small reproducer, so now I believe this is not ruby fault.


Very nice reduction indeed 👍


Vít




Regards,
Mamoru

Attachment: 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

Reply via email to